Skip to main content
Glama

get_contact

Retrieve full contact details for a person by their name.

Instructions

Get full contact details by name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:31-31 (registration)
    Tool 'get_contact' is registered in the TOOLS array on line 31 with description 'Get full contact details by name'. The actual handler is a generic stub that returns a placeholder message, since this is an inspection stub file. The real implementation lives in a native binary not present in this codebase.
    ["get_contact", "Get full contact details by name"],
  • Generic handler for all tools. All tools including 'get_contact' use the same stub handler created in the for-loop (lines 106-110). The handler accepts an empty schema `{}` and returns a static placeholder text instructing the user to install Local MCP.
    for (const [name, desc] of TOOLS) {
      server.tool(name, desc, {}, async () => ({
        content: [{ type: "text", text: "This is an inspection stub. Install Local MCP: npx -y local-mcp@latest setup" }],
      }));
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not disclose what happens if no contact is found, whether it returns one or multiple contacts, or any error conditions. The mismatch with the schema further obscures actual 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 sentence with no waste. It is concise and front-loaded with the key action.

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

Completeness1/5

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

The description claims the tool retrieves a contact 'by name,' but the input schema has no parameters, making the description incompatible. This critical omission makes the description highly incomplete and unreliable for an agent.

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?

With zero parameters, the description does not need to add parameter meaning. The baseline score of 4 is appropriate since no additional parameter info is required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Get full contact details by name,' which is clear on verb and resource, but it implies a 'name' parameter that does not exist in the input schema (empty object). This inconsistency reduces clarity and may confuse the agent.

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?

The description provides no guidance on when to use this tool versus siblings like list_contacts or search_contacts. It does not mention prerequisites, alternatives, or situations where this tool is inappropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lanchuske/local-mcp-releases'

If you have feedback or need assistance with the MCP directory API, please join our Discord server