Skip to main content
Glama
Sign In
freebox-mcp

freebox-mcp

by Nelson-PROIA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_contact_contact_id_numbers_addresses_urls_emails

Retrieve all contact numbers, addresses, URLs, and emails associated with a specific contact using its ID.

Instructions

Returns the collection of all ContactNumber for a given contact

Error codes: noent, exists, no_match

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "contact_id": "<contact_id>"
    },
    "name": "get_contact_contact_id_numbers_addresses_urls_emails"
  }
}

Input Schema

NameRequiredDescriptionDefault
contact_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • changedInput schema / properties / contact_id / type
      Previous value: -"integer"New value: +"string"
  2. Changed1 schema field changed
    • removedInput schema / properties / contact_id / description
      Removed value: -"id of the contact whose numbers/addresses/urls/emails are returned"
  3. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only mentions error codes but omits side effects, read-only nature, pagination, or any constraints, providing minimal transparency.

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

Conciseness4/5

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

The description is very short (two sentences) and directly states the core purpose and error codes. While concise, it sacrifices completeness for brevity, but the structure is efficient.

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 large number of sibling tools and the existence of an output schema, the description fails to provide necessary context about when to use this tool, its relationship to other contact endpoints, or any required preconditions.

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?

Schema has 0% description coverage for the single parameter contact_id. The description adds 'for a given contact,' which weakly implies the parameter's role but does not explain its format, constraints, or relationship to other entities.

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 clearly states that the tool returns a collection of ContactNumber for a given contact, using a specific verb and resource. However, it only mentions 'ContactNumber' while the tool name suggests it also returns addresses, URLs, and emails, causing slight ambiguity.

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 on when to use this tool versus other contact-related tools (e.g., get_contact, get_contact_id). No mention of prerequisites or alternatives, leaving the agent without context for selection.

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