Skip to main content
Glama

Default-watch and pinning service

set_pin

Set or clear (null) the pin for a platform

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>"
    },
    "name": "set_pin"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNo
platform_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries full behavioral burden. It discloses that null clears the pin, but omits permissions, idempotency, what a pin affects, side effects, and what happens for invalid or unregistered platform IDs.

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

Conciseness5/5

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

The single sentence is front-loaded and contains no wasted words. The set-or-clear distinction is delivered immediately.

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 no annotations, no output schema, and 0% parameter description coverage, the definition is too thin. An agent still lacks enough information to invoke it confidently beyond the basic platform_id target.

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%, so the description must compensate. It partially maps 'platform' to platform_id and hints that null clears the pin, but it never explains the 'model' parameter or its relationship to the pin value.

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 resource: setting or clearing the pin for a platform, including the null-clearing case. It does not explicitly differentiate from platform-related siblings like register_platform or list_platforms, but no sibling appears to overlap directly with pin management.

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?

It implies that passing null clears the pin, which is useful, but gives no guidance on when to use this tool versus alternatives, prerequisites, or whether a platform must already be registered.

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