Skip to main content
Glama
Sign In

Agent Tools API

by app.openkrill
OverviewDiscussionsAdmin

List one data collection

data_list
Read-onlyIdempotent

List one platform's collection with its own filters, for collections a plain search cannot reach (USAJOBS by department, SEC filings by CIK, OSV advisories by package). Costs 1 credit. Every row has name (platform/collection/id), kind, its fields and source {platform, url, license, attribution, fetched_at, terms_url}; quote source.attribution when you show a row.

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": {
      "platform": "<platform>",
      "collection": "<collection>"
    },
    "name": "data_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoOptional words.
filtersNoCollection filters as data_list_sources lists them, such as {"country": "VNM", "indicator": "NY.GDP.MKTP.CD"}.
platformYesPlatform id from data_list_sources, such as usajobs.
page_sizeNoRows per page, 1 to 50 (default 10).
collectionYesCollection id, such as jobs.
page_tokenNonext_page_token from the previous answer, for the next page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world behavior, so the description focuses on what they don't: cost ('Costs 1 credit') and the obligation to quote source.attribution. The row shape disclosed (name, kind, fields, source {platform, url, license, attribution, fetched_at, terms_url}) goes well beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the scope distinction in the first sentence, then gives cost and return shape. Dense but every clause carries information; only the platform/collection/id naming triplet is slightly verbose.

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?

With no output schema, the description fully covers what comes back (row fields, source block) plus the credit cost and the attribution-quoting requirement. An agent has everything needed to call this and present results correctly.

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 the schema already explains filters, platform ids and pagination with examples, so the description needn't restate them. It only adds the vague notion that filters are collection-specific, which is already implied by the 'filters' schema description.

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 ('List one platform's collection') and immediately scopes it ('with its own filters'), which separates it from the generic data_search sibling. The parenthetical examples of collections make the resource concrete.

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

Usage Guidelines5/5

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

Explicitly says when this applies — 'for collections a plain search cannot reach' — and names the alternative implicitly (plain search) with three concrete examples (USAJOBS by department, SEC filings by CIK, OSV advisories by package). This is a clear routing rule rather than implied usage.

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

All Agent Tools API 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