Skip to main content
Glama

get_contact

Look up full contact details by name from macOS Contacts. Retrieve phone numbers, emails, and addresses to integrate your local address book with AI agent workflows.

Instructions

Get full contact details by name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:82-86 (registration)
    Tool registration loop where 'get_contact' is registered with the MCP server using server.tool(). All tools in the TOOLS array are registered here with an empty schema and a stub handler.
    for (const [name, desc] of TOOLS) {
      server.tool(name, desc, {}, async () => ({
        content: [{ type: "text", text: "This is an inspection stub. Install Pilot MCP on macOS: npx -y local-mcp@latest setup" }],
      }));
    }
  • server.js:31-31 (registration)
    The 'get_contact' tool is defined in the TOOLS array with its description 'Get full contact details by name'. This is where the tool is listed for registration.
    ["get_contact", "Get full contact details by name"],
  • server.js:82-86 (handler)
    The stub handler function for all tools including 'get_contact'. Returns a placeholder message indicating this is an inspection stub and directing users to install the real Pilot MCP on macOS.
    for (const [name, desc] of TOOLS) {
      server.tool(name, desc, {}, async () => ({
        content: [{ type: "text", text: "This is an inspection stub. Install Pilot MCP on macOS: npx -y local-mcp@latest setup" }],
      }));
    }
  • Empty schema object `{}` used for all tools including 'get_contact'. No input validation is defined in this stub server.
    for (const [name, desc] of TOOLS) {
      server.tool(name, desc, {}, async () => ({
        content: [{ type: "text", text: "This is an inspection stub. Install Pilot MCP on macOS: 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 the full burden of behavioral disclosure. It does not explain what 'full details' includes, error handling if contact not found, or whether this operation has side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief and front-loaded, but the 'by name' phrase wastes space by describing a parameter mechanism that doesn't exist in the schema. Every word should earn its place, and this one misleads.

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?

Given the schema-description mismatch and lack of output schema, the description is inadequate. It doesn't explain how to identify the target contact without parameters, nor what fields are returned in 'full details'.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters, the baseline is 4, but the description mentions 'by name' implying a name parameter exists. This contradicts the empty input schema, creating confusion about how to specify which contact to retrieve.

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 the basic action (Get full contact details) and target resource, but the phrase 'by name' creates confusion since the input schema has zero parameters. It fails to differentiate from siblings like 'search_contacts' or 'list_contacts'.

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?

No guidance provided on when to use this single-contact retrieval tool versus 'search_contacts' (which supports filtering) or 'list_contacts'. The description lacks prerequisites or selection criteria.

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