Skip to main content
Glama

scribo

by io.github.causa-prima-ai

List Supported Jurisdictions

list_supported_jurisdictions
Read-onlyIdempotent

List jurisdictions Scribo can emit invoices for, with each jurisdiction's available formats and the default format applied when no override is given. Phase 1 returns Germany (DE — XRechnung / ZUGFeRD) and the United States (US — plain PDF) only. Read-only and side-effect-free; safe to call before create_invoice to confirm a country is supported. Returns an array of { jurisdiction, formats[], default_format }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint=false. Description adds value by noting side-effect-free, safe calling context, and Phase 1 limitations (only DE and US). No contradictions.

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 sentences, no waste. Purpose stated first, then behavior and usage guidance. Every sentence earns its place.

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?

For a parameterless tool with strong annotations, the description covers purpose, usage context, scope limitations (Phase 1), and return format. No gaps.

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; baseline score of 4 is appropriate. Description adds no param info, but none is needed.

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?

Description explicitly states the tool lists jurisdictions Scribo can emit invoices for, including each jurisdiction's available formats and default format. It distinguishes itself from siblings like create_invoice, get_invoice, and verify_email_code.

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?

Description explicitly recommends using it before create_invoice to confirm country support. It does not state when not to use, but for a read-only, parameterless tool, this is clear enough.

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

All scribo toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool has a clear, distinct purpose: creating invoices, retrieving them, listing supported jurisdictions, and verifying email codes. No overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (create_invoice, get_invoice, list_supported_jurisdictions, verify_email_code), making the set predictable.

Tool Count5/5

With 4 tools, the server is well-scoped for invoice generation and retrieval, covering the essential operations without excess or deficiency.

Completeness4/5

The set covers core invoice creation, retrieval, jurisdiction queries, and the verification flow. A listing tool is missing, but for a Phase 1 server focused on individual invoices, the surface is largely complete.

Resources