Skip to main content
Glama

Link contact company

link_contact_company

Vincula um contato a uma empresa (define a empresa do contato). Sincroniza nome/CNPJ da empresa no contato.

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": "link_contact_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
company_idNoID da empresa (ou vazio/omitido para desvincular)
contact_idYesID do contato

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false). The description adds a genuine side effect beyond annotations: it syncs the company name/CNPJ into the contact, which an agent needs to know before mutating. It omits that omitting company_id unlinks, but the schema covers 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?

Two short, front-loaded sentences with zero filler; the action comes first and the side effect second. Every sentence earns its place.

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

Completeness3/5

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

For a two-parameter mutation with full schema coverage and no output schema, the essentials are present. It still lacks any statement of return behavior or what happens to the contact's prior company link, leaving modest gaps.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters are documented in the schema, including the empty/omitted deslink behavior. The description adds conceptual meaning ('define a empresa do contato') but no syntax or format detail beyond the schema, so baseline 3 applies.

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?

States a specific verb+resource ('Vincula um contato a uma empresa') and clarifies the semantic effect ('define a empresa do contato'), which distinguishes it from generic update_contact. It does not explicitly name sibling alternatives, keeping it just below 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the purpose, and the schema note about empty/omitted company_id deslinking hints at the reverse operation. However, the description never states when to use this versus update_contact, nor any prerequisites such as the contact/company existing.

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.

Resources