Skip to main content
Glama
Sign In
Inserve-MCP

Inserve-MCP

Official
by inserveit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Contactpersonen zoeken

search_contacts
Read-onlyIdempotent

Find contact persons by name or email address, optionally within a specific company, to locate the right contact for your task.

Instructions

Search contacts (contact persons of companies) by name or e-mail address, optionally within one company.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPaginanummer.
queryNoFree text search on name or e-mail address.
per_pageNoAantal resultaten per pagina (max 100).
company_idNoOnly contacts of this company.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is fully covered and the description does not contradict it. The description adds only the relationship between contacts and companies; it says nothing about result volume behavior, pagination, or that unmatched queries return empty rather than erroring.

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?

A single front-loaded sentence with the resource, the searchable fields, and the optional scope, and no filler. Everything present earns its place.

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

Completeness4/5

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

For a simple read-only, zero-required-parameter search with fully documented parameters and complete annotations, the description gives an agent enough to call it correctly. The only mild gap is that no output schema exists and the description says nothing about what a contact record contains.

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 all four parameters are already documented, and the description merely mirrors that (query matches name/e-mail, company_id scopes to one company). Baseline 3 applies since the schema carries the parameter burden; no extra syntax or matching-behavior detail (e.g. partial vs exact matching) is added.

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 contacts") and immediately disambiguates the resource as "contact persons of companies," which keeps it distinct from the sibling search_companies. It stops short of naming that sibling, so an agent still has to infer which search to pick, but the entity definition itself is precise.

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 description conveys the intended query surface (name or e-mail, optionally scoped to one company), which implies when to reach for it. It offers no exclusions or pointer to the comparable sibling search_companies, and no note on when to omit the query versus browse by company_id.

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