Skip to main content
Glama
Sign In

Agent Tools API

by app.openkrill
OverviewDiscussionsAdmin

Get one data row by name

data_get
Read-onlyIdempotent

Get one row by its resource name, such as wikipedia/pages/en:Hanoi, openalex/works/W2741809807 or sec/entities/320193. 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": {
      "name": "<name>"
    },
    "name": "data_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe row's name: <platform>/<collection>/<id>.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the cost ('Costs 1 credit'), the shape of every returned row, and the source object's fields. It also gives an operational instruction to quote source.attribution when displaying a row, which is genuinely useful context an agent would not otherwise have.

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 tight sentences, front-loaded with the core action and followed by cost, return shape, and the attribution instruction. Nothing is redundant or padded.

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?

There is no output schema, and the description compensates by describing the returned row's components, including the nested source object fields. With cost, identifier format, and attribution guidance all present, an agent has everything needed to call it correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds value with concrete examples ('wikipedia/pages/en:Hanoi', 'openalex/works/W2741809807', 'sec/entities/320193') that illustrate the platform/collection/id format in practice. It doesn't explain error behavior for malformed names, so it falls short of 5.

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 ('Get one row by its resource name') and immediately grounds it with three concrete name examples. That makes it distinguishable from siblings like data_search and data_list without opening any schema.

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?

The 'by its resource name' phrasing and the sample identifiers make the usage context clear: this is an exact-identifier lookup, not a search. It stops short of naming data_search as the alternative when the name is unknown, so it earns a 4 rather than a 5.

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