Skip to main content
Glama

Get Recipe Activity Coverage

get_recipe_activity_coverage
Read-onlyIdempotent

Read coverage results for one recipe build activity.

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": {
      "activity_ref": "<activity_ref>"
    },
    "name": "get_recipe_activity_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
activity_refYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that: it does not explain what 'coverage results' contain, whether results can be stale, or how the cursor parameter affects paging, despite a cursor being present.

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, which is structurally sound. Its brevity tips into under-specification rather than wasteful verbosity, so it loses a point for thinness rather than for clutter.

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?

The tool is low-complexity, read-only, and has an output schema, so return values need not be described. However, with 0% schema description coverage, the omitted cursor semantics and lack of any guidance relative to the many sibling read tools leave meaningful gaps for an agent selecting and invoking it.

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. It implies that activity_ref identifies the recipe build activity, but it never mentions the cursor parameter at all, leaving one of two parameters completely unexplained in both schema and description.

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 names a specific verb ('Read'), a specific resource ('coverage results'), and scopes it to 'one recipe build activity,' which is enough for an agent to identify the tool's job. It stops short of differentiating itself from siblings such as get_recipe_build or list_recipe_activity_assertions, leaving the agent to infer why coverage results differ from those alternatives.

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: the phrase 'for one recipe build activity' signals the context in which the tool applies, but there is no explicit statement of when to call it, when not to, or which sibling to use instead. No prerequisites or preconditions are given.

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