Skip to main content
Glama
Sign In

Spacery

by io.github.lukehollis
OverviewDiscussionsAdmin

Link account

link_account

Links this agent to the person's account. Returns a link where the person signs in and approves a short code; call again once they have. Never ask for a password.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "link_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
link_codeNoOnly for connections without a session, the link_code from the previous call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-idempotent operation. The description adds real value beyond them: it discloses the multi-step link-and-recall behavior and the security constraint 'Never ask for a password.' This goes beyond what the structured fields convey.

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?

Three short sentences, front-loaded with the core action, then the flow, then the security caveat. Every sentence earns its place with no redundancy.

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

Completeness4/5

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

With no output schema, the description usefully explains that the tool returns a link. Combined with annotations and full schema coverage, an agent has what it needs to call it. Minor gap: it doesn't state what a successful post-approval state looks like.

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 coverage is 100% and the single optional link_code parameter is fully documented in the schema. The description alludes to the second-call flow ('call again once they have') without restating the parameter, so the schema carries the weight. 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 and resource: 'Links this agent to the person's account.' The action is unambiguous and, paired with the sibling unlink_account, the agent can infer the inverse relationship. It doesn't explicitly name or contrast the sibling, which keeps it just under 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 Guidelines4/5

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

Provides clear operational guidance: obtain the link, have the person sign in and approve a short code, then 'call again.' This two-step flow is genuinely useful context for when to invoke. No explicit exclusions or named alternatives, but the sequencing is spelled out.

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

All Spacery 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