TenderLead

Search matched tenders

search_tenders

Read-onlyIdempotent

Search tenders already matched to the signed-in TenderLead account. Does not search or modify another customer's data.

Input Schema

Name	Required	Description
`limit`	No	Maximum number of results, from 1 to 20.
`query`	No	Optional words from the tender title or buyer name.
`recommendation`	No	Optional saved TenderLead recommendation filter.

Output Schema

Name	Required	Description	Default
`tier`	Yes
`count`	Yes
`data_notice`	Yes
`opportunities`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026
- addedOutput schema / properties / opportunities / items / properties / assessment_metadata
```
Added value: +{
+  "anyOf": [
+    {},
+    {
+      "type": "null"
+    }
+  ]
+}
```
- addedOutput schema / properties / opportunities / items / properties / assessment_state
```
Added value: +{
+  "enum": [
+    "excluded",
+    "needs_review",
+    "consider",
+    "low_fit"
+  ],
+  "type": "string"
+}
```
First observedOct 17, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds useful multi-tenant context by stating it only searches the signed-in account and never another customer's data, which is meaningful behavioral disclosure beyond the annotations.

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?

Two short sentences with no waste: the first states the search scope and the second immediately bounds it to the signed-in account. The purpose and constraint are both front-loaded.

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?

The tool is a simple read-only search with a fully described input schema, annotations, and an output schema, so the description covers the essentials. The only notable missing piece is explicit routing against the sibling tools, which keeps it from being complete at the highest level.

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 the parameters limit, query, and recommendation are already fully documented. The description does not add any syntax, defaults, or interpretation beyond what the schema provides, making the baseline 3 appropriate.

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 gives a specific verb and resource ("Search tenders") and scopes it to records already matched to the signed-in TenderLead account. It clearly distinguishes this from searching other customers' data, though it does not explicitly contrast with sibling tools like get_daily_brief or get_tender_decision.

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?

It states that the tool searches already-matched tenders and does not touch another customer's data, which implies when to use it. However, it gives no explicit guidance on when to choose this over the sibling brief or decision tools, nor any when-not-to-use conditions.

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

All TenderLead tools Inspect

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

Need Help?