get_contact
Devuelve los canales públicos y el siguiente paso para contactar. No envía mensajes ni formularios.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| intent | No | ||
| language | No | es-ES |
Desafío Comunicación
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the transparency burden. It clearly discloses that the tool only returns contact channels/next steps and does not send messages or forms, implying a read-only, side-effect-free operation. However, it does not mention permissions, response behavior, or operational constraints beyond that.
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 sentences with no filler. The main action is front-loaded in the first clause, and the behavioral reassurance is compactly stated in the second sentence.
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?
The tool is simple and parameter-light, but with no annotations and no output schema, the description should explain more about what the agent should send in 'intent' and what the 'siguiente paso' looks like in the response. These gaps are material to correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description does not explain either parameter ('intent' or 'language'). Although both parameters are optional and 'language' is fixed to es-ES, the description fails to compensate for the schema gap by saying what 'intent' means or how it affects the result.
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 opens with a specific verb ('Devuelve') and a clear resource: public contact channels and the next step to contact. The explicit negation 'No envía mensajes ni formularios' distinguishes it from sending actions, but it does not directly reference sibling tools such as get_service or search, so it falls just short of full differentiation.
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?
There is no explicit guidance for when to use this tool versus its siblings. 'Para contactar' implies the use case, and the negation explains what the tool will not do, but no conditions, prerequisites, or alternative tool recommendations are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.7/5.0
Disambiguation5/5
Each tool targets a distinct resource or action: company profile, contact info, individual service, case study listing, service recommendation, and general search. The descriptions include explicit guidance on when to use search vs. recommend_service, so there is no real ambiguity.
Naming Consistency5/5
All tool names follow a clean snake_case verb_noun pattern: get_company, get_contact, get_service, list_case_studies, recommend_service. The only outlier is 'search', but as a single verb it remains consistent with the imperative verb style.
Tool Count5/5
Six tools is well-scoped for a company information service. Each tool has a clear purpose and none are redundant; the set covers information retrieval, listing, and recommendation without unnecessary bloat.
Completeness4/5
The surface covers the core public-information needs: company identity, contact, services, case studies, and a general search. A minor gap is the lack of a direct list_services tool, but search and recommend_service can find services effectively.