Skip to main content
Glama
Sign In

ToolRouter

by io.github.Humanleap
OverviewDiscussionsAdmin

Save Credential

credential_save
Idempotent

Save a credential (BYOK provider API key). Saved keys persist across sessions and are used automatically.

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": {
      "name": "<name>",
      "value": "<value>"
    },
    "name": "credential_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCredential name from the tool requirements (e.g. "ios_app_id", "openai").
labelNoHuman-readable label to identify this value (e.g. "MyApp", "Staging"). Required when saving multiple values for the same credential.
valueYesThe credential value to save.
contextNo"personal" or "team:<id>". Defaults to personal.
is_defaultNoSet this value as the default for this credential.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds genuine behavioral context beyond that: keys persist across sessions and are applied automatically. It omits overwrite/upsert behavior and any auth requirements, so it is useful but not rich.

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?

Two short sentences with zero filler; the persistence/auto-use behavior is front-loaded after the core purpose. Slightly terse rather than padded, which is the right failure mode, though it leaves room for one more clarifying clause.

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?

For a 5-param mutation with full schema coverage and no output schema, the description is adequate but thin. It conveys persistence and automatic usage, yet says nothing about overwrite semantics, team-context sharing effects, or how defaults interact with existing values — all relevant for a save operation.

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?

Schema description coverage is 100%, so all five parameters are fully documented in the schema (including the label-multiplicity rule and the context default). The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 (Save) and resource (credential), with a clarifying parenthetical that this is a BYOK provider API key, which distinguishes it from the broader credential_* family. It does not explicitly say how it differs from credential_default or credential_delete, so it falls short of full sibling differentiation.

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 says what the tool does but never states when to use it versus credential_default (for setting defaults) or credential_guide (for guidance). No prerequisites, no exclusions, no alternatives named. Usage can only be inferred from the word 'Save'.

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

All ToolRouter toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources