Discover available Accurate Online API resources such as item, vendor, and sales-order. Call this first when you need the correct resource name for a user request.
List all Accurate Online API resources available (e.g. 'item', 'vendor', 'purchase-invoice', 'sales-order'). Call this first if you don't know the resource name for what the user is asking about.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 burden. It implies a side-effect-free enumeration with no arguments, which is meaningful context, but says nothing about authentication requirements, result size, or ordering. Adequate but not rich behavioral disclosure.
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 sentences, zero filler. The verb and resource lead, examples follow, and the usage rule closes. Every clause 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 zero-parameter discovery tool with no output schema or annotations, the description supplies what an agent needs to decide to call it and what to expect (a set of resource identifiers, illustrated by examples). Minor gap: it never states explicitly that the return value is a list of names to feed into subsequent calls.
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 tool takes zero parameters, so the baseline is 4. The description correctly signals that the call is parameterless by framing it as a pure enumeration step, adding a little context beyond the empty schema.
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 ("List") and resource ("Accurate Online API resources") and concretizes it with real examples ('item', 'vendor', 'purchase-invoice', 'sales-order'). The discovery framing ("if you don't know the resource name") distinguishes it from the sibling schema_lookup, which presupposes a known resource.
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?
Gives an explicit trigger: "Call this first if you don't know the resource name for what the user is asking about," which implies the inverse condition (skip it when the resource is known). It does not name schema_lookup as the follow-up alternative, so it stops short of full when/when-not/alternatives guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.