Skip to main content
Glama
Sign In

Fawtar

by app.fawtar
OverviewDiscussionsAdmin

Fetch one record

fawtar_get
Read-only

Fetch a single record by id. For invoices this also returns the line items and the public share link.

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": {
      "resource": "<resource>",
      "id": "<id>"
    },
    "name": "fawtar_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe record's uuid.
resourceYesWhich resource the id belongs to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / resource / description
      Added value: +"Which resource the id belongs to."
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish readOnly=true and destructive=false, so the safety burden is lifted. The description usefully adds that invoice fetches include line items and a public share link, a disclosure that matters since a public link has sharing implications. It does not say what happens for an invalid id or unknown resource, or whether the resource must match the id's type.

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?

Two short sentences, front-loaded with the core action, and the behavioral detail (invoice extras) follows. There is no redundant restatement of the name or title.

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

Completeness3/5

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

With no output schema, the description is the only source of return-shape information, and it covers only invoices while 27 other resources get no indication of their response shape. It is adequate for the mechanics of the call but leaves the agent guessing about returned fields for most resources.

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 coverage is 100%, so both parameters are already documented, including the full 28-value resource enum. The description adds only marginal semantics: that id is scoped to the chosen resource and that invoice responses are enriched. Baseline 3 applies.

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

Purpose4/5

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

"Fetch a single record by id" states a specific verb and resource, and "single" implicitly separates it from the sibling fawtar_list. It stops short of naming the sibling or clarifying what a "record" spans across the 28 enumerated resources.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance: it never mentions fawtar_list as the alternative for browsing/multiple results, nor any prerequisite such as needing a uuid from a prior list call. Usage is only inferable from the phrase "by id".

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

All Fawtar 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