Skip to main content
Glama
Sign In

CryptoDecentral Sovereign MCP

by za.co.cryptodecentral
OverviewDiscussionsAdmin

Search directory

search_directory
Read-onlyIdempotent

Search directory listings by query/category/tag (unranked educational match). Education only, not financial advice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_directory"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoOptional free-text query matched against listing id, name, category, description and tags (case-insensitive). Omit to return all listings.
tagNoOptional exact tag to filter by (case-insensitive), e.g. self-custody or nostr. Omit for all tags.
categoryNoOptional exact category name to filter by (case-insensitive), e.g. Hardware wallet or Nostr client. Omit for all categories.

Output Schema

NameRequiredDescriptionDefault
countYes
listingsYes
disclaimerYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "disclaimer": {
+      "type": "string"
+    },
+    "listings": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "category": {
+            "type": "string"
+          },
+          "description": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "last_reviewed": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "license": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "type": "string"
+          },
+          "related_pillars": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "risk_notes": {
+            "oneOf": [
+              {
+                "type": "string"
+              },
+              {
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              }
+            ]
+          },
+          "sponsored": {
+            "type": "boolean"
+          },
+          "tags": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "url": {
+            "type": "string"
+          },
+          "verification": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "category",
+          "url",
+          "description",
+          "sponsored",
+          "tags",
+          "verification",
+          "last_reviewed",
+          "risk_notes",
+          "license"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "schema_version": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "disclaimer",
+    "schema_version",
+    "count",
+    "listings"
+  ],
+  "type": "object"
+}
  2. Changed3 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Optional exact category name to filter by (case-insensitive), e.g. Hardware wallet or Nostr client. Omit for all categories."
    • addedInput schema / properties / q / description
      Added value: +"Optional free-text query matched against listing id, name, category, description and tags (case-insensitive). Omit to return all listings."
    • addedInput schema / properties / tag / description
      Added value: +"Optional exact tag to filter by (case-insensitive), e.g. self-custody or nostr. Omit for all tags."
  3. 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 readOnly, idempotent, non-destructive, and closed-world behavior, so safety is covered. The description adds genuinely new behavioral context by stating results are unranked rather than relevance-sorted, plus a scope limit (education only, not financial advice). It says nothing about result caps, pagination, or whether tag and category filters combine.

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?

Single front-loaded clause states the operation and scope immediately, with no redundant restatement of the name. The trailing education/advice disclaimer is terse and earns its place as a scope boundary, though it is phrased more like legal boilerplate than operational guidance.

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 an output schema, full annotations, and 100% parameter coverage, the description only needs to convey purpose and any behavioral quirks, which it does via "unranked" and the scope caveat. The remaining gap is the relationship to the overlapping list_directory sibling, which an agent must infer.

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 description coverage is 100%, so the schema already documents each parameter's matching semantics, case-insensitivity, and omission behavior. The description reinforces this by naming query, category, and tag in the same order they appear in the schema, adding minor corroboration rather than new meaning.

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?

"Search directory listings by query/category/tag" gives a specific verb plus resource and names the three filter dimensions, matching the schema properties. It also flags the match as "unranked educational," which sets expectations about result ordering. It stops short of differentiating itself from the sibling list_directory, which appears to return the same resource.

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: the presence of q/tag/category suggests use when filtering, and "Omit to return all listings" hints it can act as a broad listing call. There is no explicit statement of when to prefer this over list_directory or search_content, nor any exclusion beyond the education-only disclaimer.

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

All CryptoDecentral Sovereign MCP 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