Skip to main content
Glama
Sign In
mcp-toolbox

mcp-toolbox

by jorgitobg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

triage_tenders

Screen recorded TED/PLACSP tenders against a fictional profile with rule-based GO/REVIEW/NO_GO verdicts and per-criterion evidence; filter by verdict or keyword offline.

Instructions

List recorded TED/PLACSP tenders screened against a fictional profile.

Rule-based GO / REVIEW / NO_GO with per-criterion evidence (open-tender-radar report, recorded 2026-11-04). Optional verdict filter and keyword query. Offline, read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "triage_tenders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
verdictNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description does real work: it discloses that the tool is offline and read-only, that data is a fixed recording dated 2026-11-04, and that screening is rule-based against a fictional profile. It stops short of describing ordering, default paging behavior, or how many tenders exist in the snapshot.

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 tight sentences, front-loaded with what the tool returns, then semantics, then the parameters. The parenthetical provenance note earns its place; nothing is 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?

An output schema exists, so return structure needn't be explained, and the description covers provenance, verdict semantics, filters, and safety profile. The only real gap is the undocumented limit parameter against a schema with no field descriptions.

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 0%, so the description must compensate. It does add real meaning by naming the verdict values (GO / REVIEW / NO_GO) for an untyped string parameter, and explains that query is a keyword filter and verdict an optional filter. The third parameter, limit, is never mentioned.

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: list recorded TED/PLACSP tenders screened against a profile, with GO/REVIEW/NO_GO verdicts. The corpus (TED/PLACSP) is clearly distinct from the BOE-oriented siblings, so an agent can tell what it returns, though siblings are never named explicitly.

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 context is implied (browse a recorded triage report, optionally filtered by verdict or keyword) and the 'Offline, read-only' note hints at safe exploration. There is no explicit statement of when to prefer this over search_boe/get_boe_document, nor any exclusion such as 'only covers tenders recorded on 2026-11-04'.

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