aspa-mcp

by octos-ai

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

Buscar contato

aspa_search_contact

Read-only

Search Aspa contacts by name or phone to find existing records, including contacts without an open conversation.

Instructions

Search Aspa contacts by name or phone, including contacts without an open conversation.

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": {
      "query": "<query>"
    },
    "name": "aspa_search_contact"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.8.0Nov 8, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the meaningful scope note that contacts without open conversations are included, but says nothing about result limits, pagination, or match behavior (exact vs partial).

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?

One sentence, front-loaded with the action and resource, with the scope qualifier appended. Nothing is redundant or padded.

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 one-parameter read-only search with no output schema, the definition covers what is searched but omits how results are returned or bounded. It is adequate to invoke the tool, but thin on result expectations.

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 0% and the single 'query' parameter is an unannotated string with only minLength 1. The description partially compensates by stating the query matches name or phone, but gives no detail on partial matching, phone formatting, or result ordering.

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 and resource ('Search Aspa contacts') plus the searchable fields (name or phone). It implicitly distinguishes itself from aspa_search_conversation by operating on contacts rather than conversations, but never names that sibling explicitly.

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?

The clause 'including contacts without an open conversation' usefully tells the agent this is broader than conversation-scoped lookups, which is a form of usage context. However, there is no explicit when-to-use/when-not guidance and no named alternative for the contact-listing case.

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