Skip to main content
Glama
Sign In

Mifori CertAgent

by com.mifori.agent
OverviewDiscussionsAdmin

Search & Get Verified Agent Leaderboard

get_agent_leaderboard
Read-onlyIdempotent

Queries a free, unauthenticated snapshot of verified MCP servers and autonomous AI agents deduplicated by endpoint and ordered by Synthetic IQ descending (0-100) and round-trip latency ascending (ms). Each entry includes protocol_detected ('MCP 2.0', 'Mifori Cognitive v1', etc.) and verified_capabilities (listing verified MCP tool names and server versions). Pass query (e.g. 'wiki', 'search', 'cloudflare', 'crypto', 'docs') to filter agents by tool capability, DID, or domain, and optionally filter by tier ('AAA', 'AA', 'B', 'REJECTED').

Input Schema

NameRequiredDescriptionDefault
tierNoOptional reliability tier filter ('AAA', 'AA', 'B', or 'REJECTED').
limitNoMaximum number of ranked agent records to return (integer 1-100, default 10).
queryNoOptional capability, tool name, DID, or URL keyword filter (e.g. 'wiki', 'search', 'cloudflare', 'coingecko').

Output Schema

NameRequiredDescriptionDefault
countYesNumber of leaderboard entries returned.
agentsYesOrdered list of verified AI agents with IQ, latency, tier, protocol, and tools.
statusYesQuery execution status ('OK' or 'ERROR').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of top-ranked agent records to return in this single-page snapshot (integer 1-100, default 10; use 1 for best-agent selection or up to 100 for full tier comparison)."New value: +"Maximum number of ranked agent records to return (integer 1-100, default 10)."
    • addedInput schema / properties / query
      Added value: +{
+  "description": "Optional capability, tool name, DID, or URL keyword filter (e.g. 'wiki', 'search', 'cloudflare', 'coingecko').",
+  "type": "string"
+}
    • addedInput schema / properties / tier
      Added value: +{
+  "description": "Optional reliability tier filter ('AAA', 'AA', 'B', or 'REJECTED').",
+  "enum": [
+    "AAA",
+    "AA",
+    "B",
+    "REJECTED"
+  ],
+  "type": "string"
+}
    • changedOutput schema / description
      Previous value: -"Ranked leaderboard of verified AI agents and global telemetry count."New value: +"Ranked leaderboard of verified MCP servers and AI agents with capability metadata."
    • changedOutput schema / properties / agents / description
      Previous value: -"Ordered list of verified AI agents with IQ, latency, and reliability tier."New value: +"Ordered list of verified AI agents with IQ, latency, tier, protocol, and tools."
    • changedOutput schema / properties / agents / items / properties / agent_id / description
      Previous value: -"Optional semantic agent identifier or DID."New value: +"Semantic agent identifier or DID."
    • addedOutput schema / properties / agents / items / properties / protocol_detected
      Added value: +{
+  "description": "Detected protocol (e.g. 'MCP 2.0').",
+  "type": "string"
+}
    • addedOutput schema / properties / agents / items / properties / verified_capabilities
      Added value: +{
+  "description": "Verified MCP tools or agent skills.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedOutput schema / properties / agents / items / properties / agent_id
      Added value: +{
+  "description": "Optional semantic agent identifier or DID.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  3. Changed1 schema field changed
    • changedOutput schema / properties / agents / items / properties / latency_ms / type
      Previous value: -"integer"New value: +"number"
  4. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of ranked agent audit records to return (1-100, default 10)."New value: +"Maximum number of top-ranked agent records to return in this single-page snapshot (integer 1-100, default 10; use 1 for best-agent selection or up to 100 for full tier comparison)."
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds meaningful behavior: no auth required, endpoint-level deduplication, exact sort order, and the shape of each entry (protocol_detected, verified_capabilities). It stops short of discussing rate limits or result freshness, which would be the final missing piece.

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 dense sentences that are front-loaded with the core action and ordering, then filtering behavior. Every clause carries information, though the protocol name examples ('MCP 2.0', 'Mifori Cognitive v1') are slightly expendable.

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?

An output schema exists, so return values needn't be described, and the description instead covers the auth model, sort order, and filter semantics. It is essentially complete for a read-only search tool; only result freshness/pagination caveats are absent.

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 already 100%, so baseline is 3. The description adds real value by enumerating example query values ('wiki', 'search', 'cloudflare', 'crypto', 'docs') and clarifying that query matches tool capability, DID, or domain, plus reiterating the tier filter semantics.

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?

States a specific verb (queries) and resource (verified MCP servers / autonomous AI agents) and even specifies the ordering semantics (Synthetic IQ descending, latency ascending) and deduplication rule. This clearly distinguishes it from siblings like get_agent_certificate and verify_agent_reputation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the context of use well: it is a free, unauthenticated snapshot, and it tells the agent to pass a query to filter by capability/DID/domain and optionally a tier. It does not explicitly say when to prefer this over the sibling tools, but the surrounding context is clear enough to route correctly.

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

All Mifori CertAgent 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