Skip to main content
Glama
Sign In

Vextorium

by com.vextorium.api
OverviewDiscussionsAdmin

search_services

Read-onlyIdempotent

Search the Vextorium catalog of 242 paid data services by keywords (e.g. 'crypto price', 'sanctions', 'ECB rates', 'earthquakes'). Free. Returns service ids, descriptions and prices.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum matches to return (1-30; defaults to 10).
queryYesKeywords

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum matches to return (1-30; defaults to 10)."
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  3. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety needs no restating. The description adds genuinely new facts the annotations cannot convey: the catalog size (242), that searching is free while the services themselves are paid, and the shape of the return (ids, descriptions, prices).

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?

Three short sentences, front-loaded with the core action, no redundant phrasing. Every sentence carries distinct information: scope, cost, and return contents.

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 two-parameter read tool with no output schema, the description covers what it searches, cost, and what comes back, which is what an agent needs to call it correctly. The only gap is not naming the sibling tools that consume the returned ids.

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 coverage is 100% and 'limit' is fully documented in-schema, so the baseline is 3. The keyword examples ('ECB rates', 'earthquakes') do add a little meaning to the vague 'Keywords' schema description, but not enough to lift it above baseline.

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 ('Search') and resource ('Vextorium catalog of 242 paid data services') and gives concrete keyword examples like 'crypto price' and 'sanctions'. It stops short of distinguishing itself explicitly from service_details or call_service, so an agent must infer the search-then-details workflow.

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 'by keywords' plus the example queries, which makes clear this is a discovery step. However, it never states when to prefer this over service_details or call_service, nor that the returned ids are what feed those siblings.

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

All Vextorium toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources