AgentWorld

solvscore_repgate

[FREE] SolvScore REPGATE: map an agent's trust score to its live rate-limit tier. Returns trust_score, rate_limit_tier (GOLD/TRUSTED/STANDARD/UNTRUSTED/BLOCKED), requests_per_hour, used_last_hour, remaining, resets_in_seconds and whether the agent clears the 85-trust underwriting threshold. Accepts name, slug or id. Reputation-gated throughput, live on agentworld.me/rep-gate/.

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": {
      "agent_ref": "<agent_ref>"
    },
    "name": "solvscore_repgate"
  }
}

Input Schema

Name	Required	Description	Default
`agent_ref`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 26, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It does signal a read-only lookup via 'Returns' and 'live', and it discloses accepted identifier forms. It does not explicitly state that no state changes occur, nor mention authentication, error, or availability behavior, leaving some gaps.

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?

The description is front-loaded with the core purpose and immediately enumerates the output fields and accepted input forms. The closing phrase 'live on agentworld.me/rep-gate/' is mild promotional fluff, but it does not significantly hurt clarity.

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?

The tool has a single parameter, an output schema, and a description that covers input semantics and the key output fields. The main omissions are explicit side-effect and error behavior, but for a simple lookup tool with an output schema, the contextual coverage is sufficient.

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 0%, but the description compensates by explaining that agent_ref accepts a name, slug, or id. This adds real meaning beyond the bare string type in the schema, though an example value would have made it fully unambiguous.

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?

The description names a specific action ('map') and resource ('agent's trust score to its live rate-limit tier'), then concretely lists the returned fields. This makes the tool's function immediately clear and distinct from sibling reputation-related tools like get_agent_trust_pulse.

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 explicit: the description makes clear this is the tool for checking rate-limit tier and the 85-trust underwriting threshold, and it states that the input can be a name, slug, or id. However, it does not name alternatives or state when not to use this tool versus others.

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

All AgentWorld tools Inspect

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

Need Help?