get_tenderThe full text of a single tender notice on BinaSmart, by its slug from list_tenders: requirements, bid bond, where and when to submit, and the link to the original notice.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Tender slug from list_tenders |
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | How to use or present this result | |
| tender | No | The tender in full, with detail | |
| source_url | No | bina.et page this result comes from; cite it |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": true,
+ "properties": {
+ "note": {
+ "description": "How to use or present this result",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "source_url": {
+ "description": "bina.et page this result comes from; cite it",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "tender": {
+ "anyOf": [
+ {
+ "additionalProperties": true,
+ "properties": {},
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "The tender in full, with detail"
+ }
+ },
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true and openWorldHint=false, so the safety profile is already covered. The description adds real value beyond them by disclosing what the payload contains (requirements, bid bond, submission place/time, original link), which helps the agent decide to fetch full text rather than a summary.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with a colon-delimited content list; every clause carries information and nothing is repeated.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, return values need not be explained, and the description still sketches the payload contents plus the slug dependency, making the tool callable without further context. Minor gap only in not contrasting with other single-item detail siblings.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the single slug parameter is already documented as coming from list_tenders. The description only restates that origin, adding no format, length, or lookup guidance 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.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('full text of a single tender notice on BinaSmart') and enumerates the content returned. The word 'single' plus the slug reference cleanly separates it from list_tenders without needing the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'by its slug from list_tenders' tells the agent this is the follow-up detail call to list_tenders, which is clear context. It gives no explicit when-not case or comparison to sibling detail tools like get_news_article or get_job, so it stops short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.