Skip to main content
Glama
Sign In
Inserve-MCP

Inserve-MCP

Official
by inserveit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Assets zoeken

search_assets
Read-onlyIdempotent

Search devices, licenses, and other configuration items by name or serial number, optionally filtered to one company, to quickly locate asset records.

Instructions

Search assets (devices, licenses and other configuration items) by name or serial number, 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_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPaginanummer.
queryNoFree text search on name or serial number.
per_pageNoAantal resultaten per pagina (max 100).
company_idNoOnly assets of this company.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and a closed-world profile, so the safety story is covered. The description adds useful context about asset types and searchable fields, but says nothing about matching semantics (partial vs exact), result ordering, or the zero-result behavior that matters for a search endpoint.

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 well-formed sentence with the resource and search fields front-loaded and the optional scope last. No filler, no repetition of schema data.

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 4-parameter, all-optional search tool with full schema coverage and read-only annotations, the essentials are present. The main gaps are the default behavior when query is absent and the shape of results (no output schema), which the description does not compensate for.

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, per_page, query and company_id are already documented in the schema, including the max 100 page size. The description restates the query and company_id meaning without adding format, matching or constraint detail beyond the schema — the baseline 3 for high coverage 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?

Uses a specific verb (search) and resource (assets), and the parenthetical 'devices, licenses and other configuration items' clarifies what counts as an asset. The searchable fields (name or serial number) are named, which separates it cleanly from sibling search tools such as search_tickets and search_companies, though no sibling is explicitly referenced.

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 phrase 'optionally within one company' implies the scoping use case, and 'by name or serial number' implies the lookup use case, so usage is inferable. However, there is no explicit when-to-use versus when-not guidance, and no mention of what happens when query is omitted (whether all assets are listed).

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