Skip to main content
Glama

Get Recipe Activity Billing

get_recipe_activity_billing
Read-onlyIdempotent

Read billing 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_billing"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
activity_refYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 it: it does not say whether billing is available only after completion, whether results are eventually consistent, or what a 'billing result' record represents. With annotations carrying the load, this is thin but not contradictory.

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?

A single front-loaded sentence with no filler; every word is on-topic. The brevity is appropriate in form, though it contributes to the under-specification noted 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?

An output schema exists, so return values need not be described, but two undocumented parameters (including pagination) and no routing against the many sibling recipe-activity tools leave real gaps for a tool this shallowly described. An agent can guess it needs an activity reference, but not how to page or when this is the right read versus coverage or build activity.

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 carries the full burden for both parameters and fails: activity_ref is only obliquely implied by 'one recipe build activity', and cursor (maxLength 512) is not mentioned at all, leaving the agent no idea that results are paginated. The schema documents types and limits but adds no semantic meaning for either field.

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 ('Read billing results') plus a scope qualifier ('for one recipe build activity'), which is far better than a tautology. It does not differentiate itself from near-neighbors such as get_recipe_activity_coverage, which presumably also reads per-activity results, so the agent cannot route between them from this text alone.

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?

There is no when-to-use guidance, no prerequisites (e.g. must the activity be complete before billing exists?), and no named alternative for related reads like coverage or build activity. The only implicit cue is the singular 'one recipe build activity' scope.

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