Skip to main content
Glama
AceDataCloud

AceDataCloud MCP Server

Official
by AceDataCloud
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

acedatacloud_create_credential

Issue a new API credential or owner grant for an application. Set spend caps, host restrictions, and expiry; confirm to activate.

Instructions

Create an API credential or owner-issued grant. Requires confirm=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNoOptional host restriction.
nameNoOptional human-readable name.
confirmNoMust be true to create the credential.
metadataNoOptional credential metadata.
expired_atNoOptional ISO-8601 expiry.
for_user_idNoUser ID to authorize; application owners only.
application_idYesApplication UUID.
limited_amountNoOptional spend cap in Credits.
allowed_api_idsNoOptional API UUID allowlist; empty means unrestricted.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed10 schema fields changedv0.1.3
    • addedInput schema / properties / allowed_api_ids
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional API UUID allowlist; empty means unrestricted.",
+  "title": "Allowed Api Ids"
+}
    • changedInput schema / properties / application_id / description
      Previous value: -"UUID of the application (subscription) to attach the key to. Required."New value: +"Application UUID."
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true to actually create the key."New value: +"Must be true to create the credential."
    • changedInput schema / properties / expired_at / description
      Previous value: -"Optional ISO-8601 expiry, e.g. '2026-12-31T00:00:00Z'."New value: +"Optional ISO-8601 expiry."
    • addedInput schema / properties / for_user_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "User ID to authorize; application owners only.",
+  "title": "For User Id"
+}
    • addedInput schema / properties / host
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional host restriction.",
+  "title": "Host"
+}
    • changedInput schema / properties / limited_amount / anyOf
      Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "minimum": 0,
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / limited_amount / description
      Previous value: -"Optional spend cap for this key, in Credits."New value: +"Optional spend cap in Credits."
    • addedInput schema / properties / metadata
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional credential metadata.",
+  "title": "Metadata"
+}
    • changedInput schema / properties / name / description
      Previous value: -"Optional human-readable name for the key."New value: +"Optional human-readable name."
  2. Addedv0.1.1

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description bears full responsibility for behavioral disclosure. It only restates the confirm requirement, which is already documented in the input schema. It does not mention side effects, permissions, idempotency, or what occurs on success/failure, leaving significant gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that immediately states the purpose and key constraint. It is appropriately concise with no filler, though it sacrifices explanatory detail for brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 9 parameters and a full output schema, the description is minimally adequate. It explains the core action and confirmation gate, but the ambiguity of 'owner-issued grant' and absence of use-case guidance reduce completeness. The rich schema partially compensates, but the description could still offer more context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides 100% parameter descriptions, so the baseline is 3. The description adds no additional meaning beyond the schema, merely echoing the confirm requirement. It does not clarify the distinctions between credential types or how to set fields like host or metadata.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states this tool creates an API credential or owner-issued grant, identifying the action and resource. While it distinguishes from sibling credential tools (list/update/delete), the phrase 'owner-issued grant' is somewhat vague and could be clearer, so it doesn't fully earn a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no explicit guidance on when to use this tool vs. alternatives, nor does it mention exclusions or prerequisites beyond the confirm requirement. The creation intent is implied by the name, but there is no contrast with other credential operations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AceDataCloud/AceDataCloudMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server