Skip to main content
Glama

Agent Nexus

by app.agentnexus
OverviewDiscussionsAdmin

Discover a callable interface for a need

discover_capabilities
Read-onlyIdempotent

Map a plain-language goal (e.g. 'send a transactional email') to callable APIs, MCP servers or CLIs. Returns {need, coverage, count, uncovered, note, matches[]}; each match has slug, endpoint, auth, formats, rate limit, pricing and a 0-100 reliability score. Never empty on a valid need: if nothing fits, coverage='none' and matches[] lists reliable starting points. Errors: an invalid or too-short need fails input validation; a backend failure returns isError=true with the message. Rate limits: 100 calls/day anonymous, 1,000/day with a free key (POST /api/public/keys, no account), 50,000/day on Agent Pro. For a known keyword or slug, use search_registry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
needYesWhat the agent is trying to accomplish, in plain language. 3-300 characters, required.
limitNoMaximum number of matching interfaces to return, 1-20. Default 5.
categoryNoRestrict to one interface layer ('api', 'mcp' or 'cli' — see list_categories). Default: omitted, searches all three.
min_reliabilityNoDrop interfaces scoring below this 0-100 reliability value. Default 0 (no filter).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
needYes
noteYes
countYes
matchesYes
coverageYes
uncoveredYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"Restrict to one interface layer. Omit to search all three (default)."New value: +"Restrict to one interface layer ('api', 'mcp' or 'cli' — see list_categories). Default: omitted, searches all three."
  2. Changed5 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Restrict to one interface layer."New value: +"Restrict to one interface layer. Omit to search all three (default)."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of matching interfaces to return, 1-20. Default 5."
    • changedInput schema / properties / min_reliability / description
      Previous value: -"Drop interfaces whose reliability score is below this value."New value: +"Drop interfaces scoring below this 0-100 reliability value. Default 0 (no filter)."
    • changedInput schema / properties / need / description
      Previous value: -"What the agent is trying to accomplish, in plain language."New value: +"What the agent is trying to accomplish, in plain language. 3-300 characters, required."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "count": {
+      "type": "number"
+    },
+    "coverage": {
+      "type": "string"
+    },
+    "matches": {
+      "items": {},
+      "type": "array"
+    },
+    "need": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "uncovered": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "need",
+    "coverage",
+    "count",
+    "uncovered",
+    "note",
+    "matches"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover safety (readOnly, idempotent), and the description goes well beyond them: full return envelope, the never-empty guarantee with coverage='none' semantics, explicit error behavior for validation vs backend failures, and three concrete rate-limit tiers including how to raise the limit.

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?

Front-loaded with purpose, then output, errors and limits in scannable order. Slightly bloated because the inline return-shape listing duplicates the existing output schema, but every other sentence carries distinct operational value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a discovery tool the agent has everything: what it returns, how to read an empty result, error modes, quota constraints, and the sibling to use instead. Nothing needed to call it correctly is missing.

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%, so the schema already documents need, limit, category and min_reliability fully. The description adds only the plain-language example for 'need' and a pointer to list_categories; no extra syntax or interaction between parameters is explained.

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 precise verb+resource ('Map a plain-language goal ... to callable APIs, MCP servers or CLIs') with a concrete example of the input shape. It is immediately distinguishable from search_registry, which it names as the keyword/slug path.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use this tool for a plain-language goal, and use search_registry when a known keyword or slug is already available. The category parameter points at list_categories as the alternative for enumerating layers.

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

All Agent Nexus toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources