Need to confirm verification details? Submit a JSON request body to retrieve verification status and information through the MoiPayWay API.
Run a verification lookup.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No | JSON request body |
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 burden of behavioral disclosure. It does not state whether this is read-only, whether authentication or prior steps are required, what side effects occur, or how results are returned. The description adds no behavioral transparency beyond the tool's name.
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 short, but this is under-specification rather than useful conciseness. The single sentence merely restates the tool name and does not earn its place because it conveys no actionable 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?
For a tool with no annotations, no output schema, one opaque free-form body parameter, and many sibling tools, a one-line restatement is far from complete. An agent lacks enough context to construct a valid request or interpret the 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?
The input schema has one top-level 'body' object, and the schema describes it as 'JSON request body' with additionalProperties allowed. Schema description coverage is 100% at the top level, so the baseline is 3, but the nested request structure is completely undefined and the description adds no parameter meaning.
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 is essentially a tautology: 'Run a verification lookup' restates the tool name 'verification_lookup' with no indication of what verification means, what entity is being looked up, or how this differs from siblings like verify_webhook. An agent cannot tell what this tool actually does.
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?
The description provides no guidance on when to use this tool versus alternatives. There are no usage conditions, prerequisites, or comparisons to sibling tools, so an agent cannot decide when verification_lookup is the correct choice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.