Skip to main content
Glama

quaderno

by io.usefulapi

List contacts

list_contacts
Read-only

List contacts (customers/vendors), newest first. Quaderno API: GET /contacts. Returns contact objects (id, kind, first_name, last_name, contact_name, email, country, tax_id, tax_status, …), wrapped as { data, pagination } when more pages exist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoSearch by contact name, email, or tax ID.
pageNoPage number (legacy pagination; prefer created_before).
per_pageNoEntries per page (1-100, default 25).
created_beforeNoCursor for pagination: return records created before this id (from X-Pages-NextPage / a prior record id).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds meaningful behavioral context: the exact endpoint, newest-first ordering, the shape of returned contact objects, and the pagination wrapper. This goes beyond the structured annotation without contradicting it.

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 tight sentences: the first defines purpose and ordering, the second gives endpoint and output shape. Every clause adds value, and the most important information is front-loaded.

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 read-only list operation with no output schema, the description sufficiently explains what is returned, the pagination envelope, and the ordering. Combined with fully described parameters and readOnlyHint, an agent has enough information to call and interpret the tool correctly.

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 100%, so the schema fully documents q, page, per_page, and created_before. The description adds context about pagination and response wrapping, but it does not need to repeat parameter-level details; the baseline of 3 is appropriate.

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 clear verb and resource: 'List contacts', plus clarifies the scope as customers/vendors and the ordering as newest first. This distinguishes it from sibling tools like get_contact, create_contact, and update_contact without ambiguity.

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?

The description implies this is the tool for enumerating/searching contacts, and the annotation readOnlyHint=true clarifies it is a safe read operation. However, it does not explicitly state when to prefer list_contacts over get_contact or mention any exclusions, leaving some inference to the agent.

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

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

A3.8/5.0
Disambiguation3/5

Most tools target distinct resources and actions, but create_invoice and create_transaction both generate tax-compliant sale documents, making their boundary unclear. calculate_tax also overlaps conceptually with the tax calculation embedded in create_transaction, though the descriptions help separate the read-only case.

Naming Consistency4/5

The set follows a consistent verb_noun pattern across get_, list_, create_, and update_ tools, with clear singular/plural usage. calculate_tax and ping fit the style, but quaderno_request is a generic escape hatch that breaks the predictable naming convention.

Tool Count3/5

At 23 tools, the server is on the heavy side and falls in the 16-25 range that feels less scoped than ideal. However, the count is somewhat justified by the many distinct entity types covered, including contacts, invoices, items, credit notes, expenses, receipts, jurisdictions, and webhooks.

Completeness3/5

Core workflows like calculating tax, creating invoices/transactions, and managing contacts/items are covered, and every exposed resource has get/list access. Missing update/delete operations for most resources, read-only webhooks, and no direct creation paths for expenses/receipts/credit notes leave notable lifecycle gaps.

Resources