Skip to main content
Glama

agent-tools (x402 + MCP + A2A directory)

get_methodology

Read-only

How every score and statistic on agent-tools.cloud is computed.

Returns the quality-score components and grade bands per protocol, the nine readiness criteria with weights, payment-evidence grades, the probing schedule and the definitions behind the daily statistics.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the genuinely useful behavioral fact: this is a static reference payload enumerating the platform's scoring rules, not computed data. It does not discuss caching, versioning of the methodology, or size of the response, which keeps it below 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.

Conciseness4/5

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

Two sentences, front-loaded with the one-line purpose before the content enumeration. The trailing list of returned artifacts is long but each item earns its place by telling the agent what topics the payload covers, which is the only thing an agent can use to decide relevance.

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 zero-parameter, read-only reference endpoint with an output schema, the description supplies everything needed: what it is, that it is static, and what subjects it covers. Minor gaps remain around how current the methodology is and whether the enumerated sections map one-to-one to fields in the response.

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 per the rubric the baseline is 4. There is nothing for the description to clarify on the input side, and it correctly adds no parameter talk.

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?

Opens with a specific statement of resource and scope: 'How every score and statistic on agent-tools.cloud is computed,' then enumerates the exact contents (score components, grade bands, nine readiness criteria, payment-evidence grades, probing schedule, statistic definitions). This clearly separates it from data-returning siblings like stats or directory_stats, which return numbers rather than the rules behind them. It falls short of a 5 only because it never names a sibling for contrast.

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 rather than stated: an agent can infer it should call this when it needs to interpret or explain a score. There is no explicit 'use this when...' framing, no statement about when not to call it, and no pointer to stats or directory_stats as the data-side alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.