Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

data_catalog

Lists all AgentWorld Data API endpoints with prices and the OpenAPI spec URL, helping you discover the full paid dataset query catalog.

Instructions

[FREE] List all AgentWorld Data API endpoints with prices and the OpenAPI spec URL. Use this to discover the full paid dataset query catalog.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the two traits that matter most here: the call is FREE (tagged in the leading token) and it returns endpoint listings with prices and a spec URL, setting up the paid tier. It doesn't describe response size or format, but it is a trivial read-only listing.

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 sentences with zero waste, and the most decision-relevant token '[FREE]' is front-loaded so an agent scanning the catalog sees the cost implication first. The second sentence exists solely to route usage.

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 no-parameter, no-output-schema discovery tool, the description says enough: what it lists, what each entry carries, and the cost model. Only the exact shape of the returned list is left unspecified, which is low-risk for a catalog call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies no input is required by framing it as a plain catalog listing.

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?

States a specific verb and resource: lists AgentWorld Data API endpoints, and specifies the payload returned (prices plus the OpenAPI spec URL). The phrase 'discover the full paid dataset query catalog' implicitly separates it from the data_* siblings, which are the paid query endpoints themselves.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use this to discover the full paid dataset query catalog' gives clear context for when to reach for it: before deciding which paid data_* tool to call. There are no explicit exclusions or named alternatives, but for a zero-parameter free catalog that is a minor gap.

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