Skip to main content
Glama
Sign In
Inserve-MCP

Inserve-MCP

Official
by inserveit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Relaties zoeken

search_companies
Read-onlyIdempotent

Search active company records by name to find MSP customers and relations, excluding archived entries. Use it to locate a company before viewing or updating its details.

Instructions

Search companies (relations / customers of the MSP) by name. Archived companies are excluded.

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_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPaginanummer.
queryNoFree text search, for example (part of) the company name.
per_pageNoAantal resultaten per pagina (max 100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world, so the safety profile is covered. The description adds genuinely new behavior: archived companies are filtered out of results, which the agent cannot learn from the schema or annotations and which affects interpretation of empty results.

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 sentences with zero waste: the core action comes first, followed by the result-set caveat. Nothing is buried or repeated.

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 three-parameter, optional-only search tool with full schema coverage and read-only annotations, the description covers purpose and the key filtering behavior. The only gap is the absence of an output schema combined with no hint about the result shape (e.g. paginated list with total count), which keeps it just short of complete.

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 page, query and per_page are all documented in the schema, including the max-100 page size and the free-text example. The description's 'by name' slightly narrows the query semantics but adds no format or matching-rule detail beyond what the schema already says; 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 and resource ('Search companies') and clarifies the Dutch domain term 'relations' as customers of the MSP, which helps disambiguate the concept. It is distinguishable from get_company by being a search rather than a single-record fetch, though the description 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?

'Search companies ... by name' implies the use case (find a company when you only know part of the name), and the archived-exclusion note implicitly tells the agent that archived records require another route. There is no explicit when-to-use/when-not guidance and no reference to alternatives such as get_company or search_contacts.

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