Skip to main content
Glama

Default-watch and pinning service

register_platform

Register a platform (tier cap: Watch 10, Fleet 50) with its initial changelog snapshot and operator-supplied price table

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": {
      "platform_id": "<platform_id>",
      "pin_class": "<pin_class>",
      "changelog": "<changelog>",
      "price_table": "<price_table>"
    },
    "name": "register_platform"
  }
}

Input Schema

NameRequiredDescriptionDefault
changelogYes
pin_classYes
platform_idYes
price_tableYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It discloses tier caps (Watch 10, Fleet 50) as a constraint, but omits permissions, idempotency on duplicate platform_id, whether registration is permanent/destructive, and error behavior for a mutation tool with a nested schema.

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?

A single front-loaded sentence with no filler. The parenthetical 'tier cap: Watch 10, Fleet 50' is dense and slightly ambiguous in phrasing but does earn its place as a constraint.

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 a mutation tool with a nested changelog object, an untyped price_table, an enum parameter, no annotations and no output schema, the description is too thin. It does not explain the pin_class choice, the required price_table shape, or the registration's side effects.

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 4 required parameters. The description only alludes to two of them (changelog, price_table) without format details, and leaves platform_id and pin_class entirely unexplained — including the meaning of PINNABLE vs ALERT_ONLY, which is the key decision the caller must make.

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?

States a specific verb (Register) and resource (a platform), and clarifies that registration bundles the initial changelog snapshot and price table, which separates it from ingest_changelog. It stops short of naming any sibling or explaining how it differs from list_platforms/probe, so it is clear but not fully differentiated.

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 gives no indication of when to call this versus alternatives such as ingest_changelog, nor any prerequisites or exclusions. The agent must infer usage entirely from the verb 'Register'.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources