Skip to main content
Glama

get_invoice

Read-onlyIdempotent

Retrieve an invoice record by providing its unique ID. Access invoice details for management or reference.

Instructions

Get an invoice record

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the invoice to retrieve

Implementation Reference

  • Handler function for the 'get_invoice' tool. Calls GET /invoices/{id} via apiGet, logs the response, and formats the result using formatShow.
    async ({ id }) => {
      try {
        const record = await apiGet<EduframeRecord>(`/invoices/${id}`);
        void logResponse("get_invoice", { id }, record);
        return formatShow(record, "invoice");
      } catch (error) {
        return formatError(error);
      }
    },
  • Input schema for the 'get_invoice' tool: requires a single 'id' (positive integer) parameter.
    description: "Get an invoice record",
    annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true },
    inputSchema: { id: z.number().int().positive().describe("ID of the invoice to retrieve") },
  • Registration of the 'get_invoice' tool via server.registerTool in the registerInvoiceTools function.
    server.registerTool(
      "get_invoice",
      {
        description: "Get an invoice record",
        annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true },
        inputSchema: { id: z.number().int().positive().describe("ID of the invoice to retrieve") },
      },
      async ({ id }) => {
        try {
          const record = await apiGet<EduframeRecord>(`/invoices/${id}`);
          void logResponse("get_invoice", { id }, record);
          return formatShow(record, "invoice");
        } catch (error) {
          return formatError(error);
        }
      },
    );
  • registerInvoiceTools is included in the central tools array in registerAllTools, which iterates and registers all tool groups.
    registerInvoiceTools,
Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating a safe read operation. The description adds no additional behavioral details such as authentication needs, rate limits, error handling, or what happens if the invoice ID does not exist.

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

Conciseness4/5

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

The description is a single sentence that is concise and directly states the action. However, it could include additional helpful context without becoming overly long.

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

Completeness2/5

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

Given no output schema and the simplicity of the tool, the description lacks information about the return format or common errors. For a retrieval operation, it would be helpful to mention what fields are returned or that it returns a full invoice object.

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% with one required parameter 'id' documented as 'ID of the invoice to retrieve'. The description does not add any additional meaning beyond the schema, so it meets the baseline for good schema coverage.

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?

The description 'Get an invoice record' clearly states the verb 'Get' and the resource 'invoice record'. It distinguishes from sibling tools like 'get_invoice_pdf' which retrieves a PDF, and 'open_invoice' which likely changes state. However, it does not specify the scope or content of the record.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., get_invoice_pdf for PDF, get_invoice_payments_by_invoice_id for payments). There are no prerequisites, exclusions, or context for when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/martijnpieters/eduframe-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server