Which corporate estate a provider belongs to, if any. Answers 200 with estate:null when the provider stands alone — that is a measured absence, not a missing record.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Provider slug — lowercase, hyphenated, as find_providers returns it, e.g. "stripe". | |
| context | No | Optional: one sentence on why you are asking. Never used to rank; read only if a result is wrong. |
Changes observed during successful MCP inspections.
Input schema / properties / context / descriptionPrevious value: -"Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable."New value: +"Optional: one sentence on why you are asking. Never used to rank; read only if a result is wrong."Input schema / properties / slug / descriptionAdded value: +"Provider slug — lowercase, hyphenated, as find_providers returns it, e.g. \"stripe\"."Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: a 200 response with estate:null signals a measured absence (provider genuinely stands alone) rather than a missing record, which is real added context beyond the annotations and schema.
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?
Two tight sentences, front-loaded with the core purpose and followed by the one edge case that matters. No filler; the clarifying clause about measured absence earns its place.
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?
There is no output schema, so the description carries the return-value burden. It explains the null case well but says nothing about the shape of a successful non-null response (e.g. estate name, slug, or id), leaving an agent partially uninformed about the positive result.
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 description coverage is 100%, so both the required slug and the optional context parameter are already fully documented in the schema. The description adds no further parameter meaning, 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 verb and resource: retrieving the corporate estate a given provider belongs to. It is clearly distinct from sibling list/lookup tools like find_estates and get_estate, though it does not name those siblings explicitly to reinforce the boundary.
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?
Usage is implied — call it when you need a provider's estate membership — but there is no explicit when-to-use/when-not guidance and no indication of how it relates to find_estates or get_estate. It does clarify the meaningful null case, which helps interpretation but not selection.
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.