Skip to main content
Glama

Record Recipe Research

record_recipe_research
DestructiveIdempotent

Replace the bounded research evidence recorded for one private build.

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": {
      "build_ref": "<build_ref>",
      "revision": "<revision>",
      "idempotency_key": "<idempotency_key>",
      "evidence": "<evidence>"
    },
    "name": "record_recipe_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
evidenceYes
revisionYes
build_refYes
idempotency_keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare destructive=true and idempotent=true, and the description's use of "Replace" is consistent with that. It adds only the scope of "one private build" and "bounded research evidence" without explaining what is destroyed, how much evidence may be supplied, or how revision conflicts are handled.

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?

The single sentence is front-loaded and free of filler. It is efficient, though its brevity contributes to the missing usage and parameter detail assessed elsewhere.

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

Completeness2/5

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

This is a destructive mutation with four required parameters at 0% schema description coverage. The description does not cover replacement semantics, prerequisites, revision concurrency, or idempotency behavior, so it is under-specified for the tool's complexity despite the output schema covering return values.

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 compensate, but it only vaguely maps to "research evidence" and "private build." It does not explain build_ref, revision, idempotency_key, or the required evidence fields, leaving the four required parameters largely opaque.

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?

The description states a specific verb and resource: replace the recorded research evidence for one private build. This clearly distinguishes it from read or append operations, though it does not explicitly name the sibling tools it differs from.

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 gives no explicit when-to-use guidance, prerequisites, or alternatives. An agent is left to infer that this is the tool for replacing existing research evidence rather than retrieving or appending it.

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