producer_servicesAuthorized broadcast offer on request: information and contacts for producers. It does not turn on streams; it only gives information and collects interest. To present a project, use contact.form_url in the browser, contact.email by e-mail, or POST /api/contact.
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | Language of the offer: pt, en, es, fr, de or hu. A missing or unknown value falls back to pt. | pt |
Changes observed during successful MCP inspections.
Input schema / properties / lang / descriptionPrevious value: -"Idioma da oferta: pt, en, es, fr, de ou hu; ausente ou desconhecido volta a pt."New value: +"Language of the offer: pt, en, es, fr, de or hu. A missing or unknown value falls back to pt."Input schema / properties / lang / descriptionPrevious value: -"Idioma da oferta: pt, en, es, fr ou de; ausente ou desconhecido volta a pt."New value: +"Idioma da oferta: pt, en, es, fr, de ou hu; ausente ou desconhecido volta a pt."Input schema / properties / lang / enumPrevious value: -[
- "pt",
- "en",
- "es",
- "fr",
- "de"
-]New value: +[
+ "pt",
+ "en",
+ "es",
+ "fr",
+ "de",
+ "hu"
+]Input schema / properties / lang / defaultAdded value: +"pt"Input schema / properties / lang / descriptionAdded value: +"Idioma da oferta: pt, en, es, fr ou de; ausente ou desconhecido volta a pt."Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely useful context beyond them: it does not start streams and only returns information and collects interest. That negative behavior is exactly the kind of trait an agent cannot infer from annotations.
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?
Three short sentences, purpose front-loaded, no filler. Slightly awkward phrasing ("Authorized broadcast offer on request") but nothing that wastes space or buries the key information.
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?
A low-complexity, single-optional-param read tool with no output schema; the description conveys what the caller gets (information and contacts) and what it does not do. No output schema exists, so return-value detail is not owed, and only minor gaps remain.
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?
One optional lang parameter with 100% schema description coverage including the enum and fallback behavior, so the schema fully carries the semantics. The description adds nothing about language selection, making the baseline 3 appropriate.
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 resource — an on-request broadcast offer providing information and contacts for producers — plus an explicit negative scope ("It does not turn on streams"). It distinguishes itself from generic contact/info siblings, though the phrase "authorized broadcast offer" is slightly opaque.
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?
Names concrete alternatives (contact.form_url in browser, contact.email by e-mail, POST /api/contact) and the condition that selects them ("To present a project"). No explicit statement of when the agent should prefer this tool itself, so it stops short of the top band.
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.