Skip to main content
Glama

record_research_step

Idempotent

Record one research request selection step for aggregate completion counts. No holdings or report arguments are stored.

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": {
      "step": "<step>",
      "flow_id": "<flow_id>"
    },
    "name": "record_research_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepYes
flow_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so the description's added value is disclosing what is and is not persisted: only aggregate step counts, with no holdings or report arguments stored. That is meaningful context for an agent worried about leaking sensitive data into a write call. It stops short of saying whether writes are idempotent-by-key or what the call returns.

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?

Two short sentences with no waste: the action and its purpose come first, the storage exclusion second. Nothing is repeated from annotations or the schema.

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?

It is a simple two-parameter, output-schema-less tool, and the description correctly conveys scope and data-handling boundaries. However, with zero schema coverage the definition leaves both parameters unexplained, so an agent still lacks enough to call it confidently without opening the schema.

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 carry parameter meaning, and it does not. The word 'step' hints at the `step` parameter but never explains the enum values symbol/type/confirm, and `flow_id` (a 32-hex string) is not mentioned at all. An agent must read the raw schema to know what to pass.

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: 'Record one research request selection step'. The trailing clause 'for aggregate completion counts' explains why the record exists, and 'No holdings or report arguments are stored' scopes what this tool is not. It never names a sibling, so differentiation is by scope description rather than explicit contrast.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is called while stepping through a research request selection flow, since a 'step' is recorded. There is no explicit when-to-call, no mention of ordering relative to get_research_request_options or submit_research_request, and no stated prerequisites.

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