Skip to main content
Glama
Sign In

TenderCrest AI

by io.github.tendercrestai
OverviewDiscussionsAdmin

Search evidence

search_evidence
Read-only

Search the signed-in user's own company evidence for one organization by meaning, using the same semantic search as the web app. Returns matching evidence with citations. 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>",
      "query": "<query>"
    },
    "name": "search_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdYesOrganization ID from list_organizations.
queryYesSearch text, up to 2000 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds genuinely new behavioral facts beyond that — the results are scoped to the signed-in user's own company, matching is semantic rather than keyword, results come back with citations, and an account is required. It does not mention result caps or pagination, which is the main remaining gap.

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?

Three short sentences, front-loaded with what is searched and returning the citation detail last; nothing is redundant. The trailing account requirement is slightly abrupt but earns its place as a precondition.

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 simple two-parameter read tool with no output schema, the description covers scope, retrieval mode, return shape ('with citations'), and authentication. Only result-set size and pagination behavior are left unstated.

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 orgId and query are already documented, and the description adds only mild framing ('one organization', 'by meaning'). It offers no additional format or syntax detail beyond the schema, so the baseline 3 applies.

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 and resource ('Search ... evidence') and qualifies the retrieval mode as semantic ('by meaning'), which distinguishes it in spirit from a plain list operation. It stops short of naming the sibling tools (list_evidence, search_opportunities) that an agent would otherwise confuse it with.

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: 'by meaning' and 'same semantic search as the web app' suggest a meaning-based retrieval tool, and the scope constraint ('one organization') limits it to a single org. There is no explicit statement of when to choose this over list_evidence or read_evidence_source, and no stated exclusions.

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