compare_tableEach option's value on every criterion of the US 409A valuation providers and cap table platforms comparison — the full table.
| Name | Required | Description | Default |
|---|---|---|---|
| option | No | one option's name, else all |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry behavioral disclosure. It states the output is the full comparison table with no hidden filtering, but it does not describe output format, pagination, size, or any other invocation-relevant behavior.
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 sentence that conveys content, scope, and domain context without repeating the title. Every phrase 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?
For a simple one-parameter tool the description is mostly adequate, but with no output schema and no annotations, an agent still lacks detail about the return shape and has no guidance for selecting among compare_table, compare_criteria, and compare_options.
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%, so the schema already documents the only parameter, 'option'. The description adds no parameter-specific meaning, which matches the baseline of 3; no compensation is needed.
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?
The description clearly identifies what the tool returns: every option's value on every criterion, presented as the full table. It distinguishes itself from sibling tools like compare_options and compare_criteria by emphasizing the complete matrix, though it lacks an explicit verb.
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 guidance is given about when to use this tool versus the sibling tools. The phrase 'full table' implies use when a complete view is needed, but there are no explicit conditions, exclusions, or alternative routing.
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.
The compare_* tools are clearly separated: criteria defines the axes, options lists the entities, and table joins them into the full matrix. The enquiry_* tools are equally distinct: describe explains the process, fields defines the schema, and submit_enquiry executes the two-step submission.
The compare_* tools follow a consistent prefix convention, and enquiry_describe/enquiry_fields follow the same noun-first pattern. submit_enquiry breaks that pattern by leading with a verb instead of the enquiry_ prefix, though it remains clear and predictable.
Six tools is well-scoped for this server's purpose: three tools cover the comparison matrix and three cover the enquiry workflow. Each tool earns its place without redundancy or bloat.
The comparison surface is complete: an agent can discover criteria, filter options, and view the full evaluation table. The enquiry workflow is also complete, covering explanation, schema discovery, validation, consent, and confirmation-token submission.