Skip to main content
Glama
Sign In
Gantry

Gantry

by fourn9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_bot_context

Read-only

Retrieves bot execution context for a given session, role, and state, helping agents resume or evaluate robotics work with the correct state and intent.

Instructions

get bot context

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": {
      "arguments": "<arguments>"
    },
    "name": "get_bot_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
argumentsYes
idempotency_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.4.0

TDQS

D1.1/5.0
Behavior1/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered, but the description contributes nothing beyond that. It says nothing about what is retrieved, whether missing session/state IDs cause an error or an empty result, or how the nested basis/intent objects are populated.

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

Conciseness2/5

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

Three words with no filler, but the brevity comes from under-specification rather than discipline. There is nothing front-loaded or structured because there is essentially no content.

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

Completeness1/5

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

The tool takes a nested payload with five inner fields, has no output schema, and has no parameter documentation anywhere. A readOnlyHint is not sufficient context for an agent to form a valid, correctly scoped call.

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

Parameters1/5

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

Schema description coverage is 0% and the schema is nested: `arguments` requires session_id, role, and state_id, plus optional basis and intent objects, and an idempotency_key — all entirely undescribed in both schema and description. With 0% coverage the description must compensate, and it does not address a single parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

"get bot context" is a verbatim restatement of the tool name with no additional specificity. It never says what "bot context" contains, what entity it is scoped to, or how it differs from any of the dozens of sibling read tools such as `context`, `state`, or `session_details`.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

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

There is no when-to-use guidance, no prerequisites, and no mention of any alternative. An agent facing a catalog containing `context`, `review_context`, `related_review_context`, and `get_persistent_bot` has no basis for choosing this one.

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

Deploy Server

Other Tools