Skip to main content
Glama

Ver contacto

get_contact
Read-onlyIdempotent

Devuelve los canales oficiales de contacto de Kroel Graphics. Úsala cuando alguien quiera escribirle, seguirlo o saber dónde está. Devuelve el enlace y número de WhatsApp, el formulario de cotización, Instagram, Facebook, Behance, LinkedIn, la ubicación y los idiomas de atención.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
behanceNo
idiomasNo
facebookNo
linkedinNo
telefonoYes
whatsappYes
instagramNo
ubicacionNo
formularioYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds no behavioral context beyond that — nothing about freshness of the contact data, whether it varies by locale, or what happens on failure. Enumerating the returned fields is largely redundant because an output schema already exists.

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 with the capability stated first and the triggering intents second, followed by the payload inventory. No filler, no restating of the tool name, and every clause carries information.

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?

For a zero-parameter, read-only, closed-world lookup with a full output schema and rich annotations, the description covers what an agent needs in order to select and call it. The only remaining gap is the lack of routing against send_quote_request when a user actually wants to submit a quote rather than just find the contact channel.

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?

The tool takes zero parameters and the schema is a closed empty object, so there is nothing for the description to disambiguate. Baseline of 4 applies; it would only reach 5 if it explicitly stated that no arguments are needed, which it does not.

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 names a specific verb+resource ("Devuelve los canales oficiales de contacto de Kroel Graphics") and enumerates exactly what those channels are (WhatsApp, formulario de cotización, Instagram, Facebook, Behance, LinkedIn, ubicación, idiomas). This makes the tool's scope clear. It stops short of a 5 because it never explicitly distinguishes itself from siblings like get_services or send_quote_request, and the mention of "formulario de cotización" could momentarily blur the line with the quote tools.

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?

"Úsala cuando alguien quiera escribirle, seguirlo o saber dónde está" gives three concrete triggering intents, which is genuine when-to-use guidance. There is no explicit when-not guidance or named alternative (e.g., pointing to send_quote_request for actually submitting a quote), so it falls one step short of a 5.

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.