Skip to main content
Glama

Ruling

Get agent facts

get_agent
Read-only

Facts about one AI agent on Ruling: pricing, platforms, integrations, license, repo, and the community score out of 10 (null until it has published community reviews).

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": {
      "slug": "<slug>"
    },
    "name": "get_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesAgent slug, e.g. claude-code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 semantics by stating the community score is out of 10 and is null until reviews are published, but it says nothing about error behavior for a nonexistent slug or about result freshness.

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?

One sentence, front-loaded with the resource and followed by the returned fields, with zero filler. The parenthetical caveat about the null score is appended where it belongs.

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 simple one-parameter read tool with no output schema, the description usefully enumerates the return payload and explains the null case, which is more than most getters provide. Only the not-found behavior is left unstated, a minor gap given the low complexity.

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 description coverage is 100% and the slug parameter carries a pattern and an example, so the schema does the work. The description adds no additional meaning about the slug format or normalization beyond what is already structured.

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 resource plus an enumeration of what is returned (pricing, platforms, integrations, license, repo, community score), so the agent knows exactly what this lookup yields. The singular "one AI agent" implicitly contrasts with search_agents and compare_agents, though it never names them.

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: a single-agent lookup keyed by slug, as opposed to the sibling search/compare tools. There is no explicit statement of when to prefer this over search_agents, and no mention of prerequisites or what happens when the slug is unknown.

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