Skip to main content
Glama
Sign In
invovate-mcp-server

invovate-mcp-server

by LightSpeedPlusOne
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_invoice_capabilities

Retrieve supported invoice languages, PDF templates, and features. Use this to pick valid language, template, and currency values.

Instructions

List what the Invovate invoice API supports: languages, PDF templates, and notable features. Use this to pick valid language/template/currency values.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_invoice_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It correctly describes a read-only listing operation with no destructive or authorization concerns, though it could mention that it is a safe, idempotent call.

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 short, front-loaded sentences with no wasted words. Each sentence provides essential information about purpose and usage.

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

Completeness5/5

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

Given zero parameters and no output schema, the description is complete. It explains what the tool returns and how to use it, and sibling tools provide additional context for when to invoke this one.

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

Parameters4/5

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

No parameters exist, so the input schema is fully covered. The description adds value by specifying what the tool lists, which is sufficient.

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 explicitly states the tool lists supported languages, PDF templates, and notable features for the Invovate invoice API, distinguishing it clearly from sibling tools that calculate or generate invoices.

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

Usage Guidelines4/5

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

The description advises using this tool to pick valid language/template/currency values, providing clear context for its use. It does not explicitly state when not to use it or mention alternatives, but the sibling tools make the distinction clear.

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

Deploy Server

Other Tools