Skip to main content
Glama
Sign In

Agent Tools API

by app.openkrill
OverviewDiscussionsAdmin

List comments under a post

data_list_comments
Read-onlyIdempotent

List the replies or comments under one post, given the post's name, such as bluesky/posts// or stackexchange/posts/stackoverflow/11227809. Costs 1 credit.

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": {
      "post": "<post>"
    },
    "name": "data_list_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
postYesThe post's name.
page_sizeNoRows per page, 1 to 50 (default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so safety is covered. The description adds a genuinely new behavioral trait — 'Costs 1 credit' — which an agent needs for cost-aware selection. It doesn't cover ordering or threading of replies, so not a 5.

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, zero waste: purpose and argument shape first, cost last. Every clause earns its place.

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-only list tool with no output schema, this covers purpose, identifier format and cost. Remaining gaps are minor (pagination defaults are in the schema; ordering is unstated).

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 would be 3, but the description goes beyond the schema's bare 'The post's name' by showing two concrete identifier formats (bluesky/posts/<did>/<rkey>, stackexchange/posts/stackoverflow/11227809). That materially helps an agent construct a valid value.

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?

Specific verb+resource: 'List the replies or comments under one post'. It names the resource precisely and gives example identifiers, making it clearly distinct from data_get (single item) or data_search. It does not explicitly name a sibling to differentiate from, which keeps it just under a 5.

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?

The description implies when to use it — 'given the post's name' — but gives no explicit when-not conditions or alternatives such as data_list or data_get for related cases. Usage is inferable rather than stated.

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