Retrieve all custom formulas and calculated variables in a Web Intelligence document to inspect, audit, or troubleshoot calculations using its Webi document ID.
Retrieves all custom formulas and calculated variables defined inside a Webi document.
| Name | Required | Description | Default |
|---|---|---|---|
| webi_doc_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It implies a read operation and scopes results to a Webi document, but says nothing about required permissions, whether the document must be open/refreshed, error behavior for invalid IDs, or result size. For a zero-annotation tool this is a significant gap.
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?
One front-loaded sentence with no filler; the verb and scope come first. It is efficiently written, though the terseness reflects under-specification rather than optimal density.
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?
An output schema exists, so return values need not be described. However, with no annotations and an undocumented parameter, the description leaves the agent guessing about access requirements and invocation preconditions for this read tool.
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 0% and the single parameter webi_doc_id is undocumented in the schema. The description implies the ID refers to a Webi document, but adds no format, source, or validity details to help the agent supply a correct value.
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?
Clear specific verb+resource: retrieves custom formulas and calculated variables. This distinguishes it from siblings like get_doc_parameters, get_reports, and get_report_elements, which cover different document artifacts. It stops short of explicitly naming an alternative, so 4 rather than 5.
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?
No when-to-use guidance, no prerequisites, and no mention of sibling tools such as get_doc_parameters or get_dp_specification. The agent must infer from the purpose alone when this tool is the right choice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.