Skip to main content
Glama
Sign In

TenderCrest AI

by io.github.tendercrestai
OverviewDiscussionsAdmin

List evidence

list_evidence
Read-only

List the signed-in user's own company evidence for one organization: uploaded source documents and saved answers with their approval state. Only returns evidence the user's organization owns. Needs a TenderCrest account.

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": {
      "orgId": "<orgId>"
    },
    "name": "list_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdYesOrganization ID from list_organizations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries the rest and does add real context: the result set is limited to what the user's organization owns, each item carries an approval state, and an account (auth) is required. What is missing is operational behavior such as pagination, result limits, or ordering, which matters for a list tool.

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?

Three short sentences, front-loaded with what is returned, then ownership scope, then the auth precondition. Every sentence carries distinct information and there is no filler.

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

Completeness4/5

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

For a one-parameter read tool with full schema coverage and a readOnlyHint, the description covers the returned entities, the ownership boundary, and the account requirement, which is enough to call it correctly. It lacks only pagination/result-size behavior, which no output schema supplies either.

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 coverage is 100% and the sole parameter orgId is already documented as coming from list_organizations. The description adds only that the call is scoped to exactly one organization, which is essentially implied by a single required orgId; it adds no format or edge-case meaning beyond the schema.

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 (list) and a precisely scoped resource: the signed-in user's own company evidence for a single organization, covering both uploaded source documents and saved answers with approval state. That is far more than a restatement of the name. It stops short of 5 because it never names the sibling list/search tools (search_evidence, read_evidence_source) as the alternatives an agent should consider instead.

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 implied rather than stated: 'for one organization' and 'Only returns evidence the user's organization owns' signal the listing/ownership scope, and 'Needs a TenderCrest account' gives a prerequisite. But there is no explicit when-to-use versus search_evidence or read_evidence_source, and no statement of when this tool should not be used.

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