Skip to main content
Glama
Sign In
Cuéntica MCP

Cuéntica MCP

by dacmail
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_company

Read-onlyIdempotent

Retrieves business details such as name, tax ID, address, invoice series, and logo from the accounting system.

Instructions

Datos del negocio: nombre, CIF, dirección, series de facturación, logo.

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_company"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already communicate readOnlyHint and idempotentHint, so the description adds limited new behavioral context beyond listing returned fields. It does not disclose potential authorization needs, data source, or cache behavior.

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 a single concise sentence that is front-loaded and contains no redundant information. Every word is necessary.

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

Completeness4/5

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

Given the zero parameters, clear annotations, and existence of an output schema, the description is sufficient for a simple retrieval tool. It covers the key fields returned, though it could mention that this is the user's own company data.

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?

There are no parameters in the input schema (100% coverage), so the description does not need to add parameter meaning. The baseline of 4 is appropriate as it adds no confusion.

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 clearly states the tool returns 'Datos del negocio: nombre, CIF, dirección, series de facturación, logo' (business data: name, tax ID, address, billing series, logo), which is a specific verb and resource. It distinguishes from siblings as other get_* tools are for different entities (e.g., customer, account).

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 implies usage for retrieving company data, and sibling tools clarify alternatives for other entities. However, it does not explicitly state when to use this tool versus others or any prerequisites.

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