Attach trust-oracle reputation scores (party -> [0,1]) as ruling inputs.
| Name | Required | Description | Default |
|---|---|---|---|
| scores | Yes | ||
| case_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
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?
Since annotations are absent, the description must explain behavioral traits. It does not disclose whether scores overwrite existing ones, require permissions, or have side effects. Only the basic attach action is mentioned.
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?
The description is a single concise sentence that front-loads the action. It is efficient but could include additional context without becoming verbose.
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?
Given the nested object parameter, lack of annotations, and context of sibling tools, the description is incomplete. It does not explain the output schema or how scores integrate with other tools, leaving gaps for proper usage.
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?
The description adds meaning to the 'scores' parameter by specifying it maps parties to numbers in [0,1]. However, the 'case_id' parameter is not elaborated, and the schema coverage is 0%, so more detail would be beneficial.
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 states the verb 'attach', the object 'trust-oracle reputation scores', and the purpose 'as ruling inputs'. It distinguishes this tool from siblings like 'rule' and 'submit_evidence' by specifying the type of input.
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 provided on when to use this tool versus alternatives such as 'submit_evidence' or 'rule'. The description does not mention prerequisites or when to avoid using it.
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.
Each tool has a clear, distinct purpose: filing cases, querying, submitting evidence, setting trust scores, ruling, and verifying. No overlap or ambiguity.
All tool names use consistent snake_case with a verb_noun pattern (e.g., file_case, get_case, submit_evidence). Even 'rule' is a concise verb that fits the pattern.
8 tools is well-scoped for an arbitration server: covers filing, evidence, trust, ruling, verification, and querying. Neither too few nor too many.
The tool surface covers the full arbitration lifecycle: case creation, evidence submission, trust score input, ruling, verification, and case listing/retrieval. No obvious gaps.