Skip to main content
Glama
Sign In

TenderCrest AI

by io.github.tendercrestai
OverviewDiscussionsAdmin

Read a shred result

get_shred_result
Read-only

Read the result of a shred_rfp job using its result token. Returns the status and, when complete, the numbered requirements, the gap preview, and any warnings. Free, no sign-in.

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": {
      "token": "<token>"
    },
    "name": "get_shred_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesResult token returned by shred_rfp.
resumeNoSet true to restart a stalled job.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With readOnlyHint=true already declaring safety, the description adds real context beyond annotations: no authentication or cost barrier, and a partial-result contract where requirements and gap preview only appear once the job is complete. It does not address token lifetime, polling behavior, or the effects of restarting a stalled job via the resume flag, which is the one behavior an agent could trip over.

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?

A single front-loaded sentence pairs the action with the return contract, and the trailing access note is short and useful. Nothing is repeated or padded.

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

Completeness5/5

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

There is no output schema, so the description must carry the return shape, and it does: status first, then numbered requirements, gap preview, and warnings when complete. Combined with annotations covering safety and the schema covering both parameters, an agent has enough to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters are already documented, including the token's origin and the resume flag's purpose. The description reinforces the token's link to shred_rfp but adds no new semantics (format, expiry, or when resume is appropriate), so the baseline 3 is appropriate.

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

Purpose5/5

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

States a specific verb and resource ('Read the result of a shred_rfp job') and explicitly anchors it to its producing sibling, shred_rfp. It also enumerates what comes back (status, numbered requirements, gap preview, warnings), so an agent knows exactly what this tool yields versus other get_* result readers in the catalog.

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

Usage Guidelines4/5

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

'using its result token' plus the token's origin in shred_rfp makes the triggering condition clear: call this after a shred job exists. The 'Free, no sign-in' note removes a common gating question. It stops short of stating polling cadence or what to do while status is incomplete, so it is clear context rather than explicit when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TenderCrest AI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources