Skip to main content
Glama
Sign In

Vextorium

by com.vextorium.api
OverviewDiscussionsAdmin

service_details

Read-onlyIdempotent

Details of one Vextorium service: what it does, its price in USDC, the JSON input it accepts (schema) and an example. Free.

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": {
      "service": "<service>"
    },
    "name": "service_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceYesService id from search_services, e.g. 'crypto-price'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changed
    • changedInput schema / properties / service / description
      Previous value: -"Service id from search_services, e.g. 'token-safety'"New value: +"Service id from search_services, e.g. 'crypto-price'"
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this is read-only, idempotent, closed-world, and non-destructive. The description adds useful behavioral context by listing what the response contains and noting that the call is free, though it does not mention failure behavior or rate limits.

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?

The description is a single, front-loaded sentence with no wasted wording. It gives the resource, the returned fields, and the cost in one compact line.

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

Completeness5/5

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

For a simple read-only lookup with one fully documented parameter and rich annotations, the description is complete enough. Although no output schema exists, the description enumerates the key return values so an agent knows what to expect.

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?

There is only one parameter, and schema coverage is 100%; the schema fully documents that it is a service id from search_services with an example. The description does not add parameter-specific meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and scope: details of one Vextorium service. It enumerates the returned content (what it does, USDC price, JSON input schema, example), making it clearly distinct from search_services and call_service.

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 'Details of one Vextorium service,' but the description does not explicitly say when to use this instead of search_services or call_service. The 'Free' note adds context but does not provide routing guidance.

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