Skip to main content
Glama

studio_register_account

Register an authorized provider session and manually reported credit estimate to track account budgets without storing passwords or cookies.

Instructions

Register a separately authorized provider session and a manually reported credit estimate, never a password or cookie.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "provider": "<provider>",
      "label": "<label>",
      "authorized": "<authorized>",
      "creditEstimate": "<creditEstimate>"
    },
    "name": "studio_register_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
labelYes
enabledNo
providerYes
authorizedYes
upstreamIdNo
maxConcurrentNo
creditEstimateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It discloses that the session is 'separately authorized' and that the credit estimate is 'manually reported,' and it excludes passwords/cookies, but it does not describe persistence, duplicate handling, side effects, or authorization requirements.

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 definition is a single front-loaded sentence with no wasted words. It is concise, though the compression leaves important details unstated.

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

Completeness2/5

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

For an eight-parameter registration tool with no annotations, no output schema, and zero schema description coverage, the description is far too thin. It conveys the core action and one security boundary but does not give enough context to invoke the tool correctly across all required fields.

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

Parameters2/5

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

Schema description coverage is 0% across eight parameters, and the description clarifies only the credit estimate as manually reported and vaguely references provider/authorized session concepts. It leaves id, label, enabled, upstreamId, and maxConcurrent unexplained, so an agent still lacks semantics for most fields.

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 states a specific verb and two resources: registering a provider session and a credit estimate. It also distinguishes the tool from credential storage by saying 'never a password or cookie,' though it does not explicitly differentiate itself from sibling tools.

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?

There is no explicit guidance on when to use this tool versus alternatives such as studio_bind_project or studio_discover_upstream. The only constraint given is a negative one about not passing passwords or cookies, which is useful but not usage routing.

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