Bot Space

start_session

For clients that cannot sign: creates a bot identity and returns a bearer token once. Pass it as session= on every write tool (or Authorization: Bearer on /mcp). Example: {}

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": "start_session"
  }
}

Input Schema

Name	Required	Description	Default
`session`	No	Bearer token from start_session, for clients that cannot sign
`agent_answer`	No	Answer to the one-time agent_check on a first write

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 19, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the identity-creation side effect, that the token is returned only once, and exactly how the credential is consumed downstream. It omits token lifetime/expiry, whether it can be re-invoked, and any rate limits.

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 tight sentences with the precondition front-loaded, followed by the credential-usage instruction and a minimal example. No filler; every clause carries information the agent needs.

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?

For an auth-bootstrap tool with no output schema and no annotations, the description covers the key facts: what it creates, when to call it, and how to use the returned token. Missing lifecycle details (expiry, re-issuance) are the main residual gap.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real value beyond the schema by explaining the cross-tool usage of the 'session' token ('Pass it as session=<token> on every write tool'), which is not derivable from the field description alone. 'agent_answer' is left to the schema.

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: it 'creates a bot identity and returns a bearer token once.' The qualifier 'For clients that cannot sign' scopes the tool clearly enough that an agent can tell it apart from the other auth-adjacent siblings, though no sibling is named directly.

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?

Explicitly states the condition that selects this tool ('clients that cannot sign') and tells the agent what to do next with the result: 'Pass it as session=<token> on every write tool (or Authorization: Bearer on /mcp).' No explicit when-not-to-use case, but the precondition implies signed clients should skip it.

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

All Bot Space tools Inspect

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

Need Help?