Skip to main content
Glama

Ruling

Compare two agents

compare_agents
Read-only

Side-by-side facts and community scores for two AI agents on Ruling, plus the link to the full comparison page.

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": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "compare_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesAgent slug, e.g. claude-code
bYesAgent slug, e.g. claude-code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/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 genuinely useful return content — facts, community scores, and an external link to the full comparison page — but says nothing about how invalid or non-existent slugs are handled, even though both parameters are required.

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?

A single sentence with no filler, and the return contents are front-loaded. Minor cost: 'on Ruling' and the marketing tone of 'community scores' add little operational information.

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?

With only two well-documented string parameters, no nested objects, and a read-only annotation profile, this is nearly complete. Since there is no output schema, the brief description of returned content does enough to set expectations.

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%: both 'a' and 'b' are documented with slug format, pattern, and an example. The description mentions 'two AI agents' but adds no slug guidance or ordering/deduplication semantics beyond what the schema already states, so the baseline of 3 applies.

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?

The description names a concrete verb-and-resource pairing: side-by-side comparison of two AI agents, with the specific outputs (facts, community scores, link to the full comparison page). 'two AI agents' scopes it away from the single-agent sibling get_agent, though it never names that sibling explicitly.

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 only implied by the phrase 'two AI agents' — an agent can infer this is the multi-agent comparison tool rather than a lookup, but there is no explicit when-to-use or when-not-to-use (e.g. 'use get_agent for a single agent, search_agents to discover slugs first').

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.

Resources