Skip to main content
Glama
Sign In
ThriftyRelay

ThriftyRelay

by Roseu7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Approval Step Detail

approval_step
Read-only

Fetches one approval step body, capped for display, by task ID and index so users can review internal approval card details.

Instructions

Internal approval card detail source. Returns one step body, capped for display.

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": {
      "task_id": "<task_id>",
      "index": "<index>"
    },
    "name": "approval_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexYes
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnly, non-destructive, closed-world behavior, so the safety profile is covered. The one added fact — output is 'capped for display' — is genuinely useful truncation context, but it isn't quantified and nothing is said about access restrictions on 'Internal' data.

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?

Two short, front-loaded sentences with no filler. The brevity is efficient, though it shades into under-specification rather than model conciseness.

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?

No output schema, zero parameter documentation, and a patterned task_id plus a numeric index the description doesn't explain. For a two-required-parameter lookup tool, this leaves the agent guessing how to construct or interpret the call.

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?

Both parameters are required and schema description coverage is 0%, so the description is the only place meaning could be added — yet it never mentions task_id or index. It doesn't even hint that index selects which step within a task.

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

Purpose3/5

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

States that it returns a single approval step body, which gives a verb-plus-resource reading, but the phrase 'Internal approval card detail source' is jargon that doesn't clearly distinguish it from siblings like pending_approvals or remote_inspect.

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?

No indication of when to use this instead of pending_approvals, open_approval, or remote_inspect, and no prerequisites are mentioned. The agent must infer usage purely from the name.

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