Skip to main content
Glama
Sign In

InvoiceParser Pro

by com.invoiceparserpro
OverviewDiscussionsAdmin

Find saved documents

search_documents
Read-onlyIdempotent

Search saved documents by filename, supplier or printed reference, subject to your document permissions. Returns one bounded page; no new processing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "input": "<input>"
    },
    "name": "search_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With annotations already declaring readOnlyHint=true, idempotentHint=true, and destructiveHint=false, the description adds useful context: results are permission-scoped and limited to one bounded page. It also states there is no new processing, reinforcing the side-effect-free nature beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two compact clauses, front-loads the core action and searchable fields, and has no wasted language. Every phrase contributes to purpose, permissions, or return scope.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only search tool with annotations covering safety and no output schema, the description is nearly complete: it covers scope, permissions, and bounded pagination. It leaves minor gaps around offset semantics and what a result page contains, but an agent can invoke this tool correctly from the definition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description should compensate. It explains what the query searches over (filename, supplier, printed reference) and that a bounded page is returned, but it does not explain the offset parameter or pagination behavior despite offset being in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb-resource pair: search saved documents. It also names the searchable fields (filename, supplier, printed reference), which clearly distinguishes it from retrieval tools such as get_document and from search_invoices.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies the tool is for locating saved documents by several fields, but it does not explicitly say when to use this instead of get_document or search_invoices. No exclusions or alternative-routing guidance are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All InvoiceParser Pro toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources