Skip to main content
Glama
Sign In

Dagon Inference

by io.github.inkwell-finance
OverviewDiscussionsAdmin

Create a Dagon API key

dagon_create_key

Create a new Dagon account key (POST /v1/keys). No API key needed. The secret is shown only once: store it securely and configure your MCP connection to send it as Authorization: Bearer <key>; never paste it into shared chats or files under version control.

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": "dagon_create_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoLabel for the key, up to 80 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare this is a non-read-only, non-idempotent, open-world write, but the description adds the crucial facts annotations cannot: the call is unauthenticated and the returned secret is displayed only once, with concrete instructions on how to use it (Bearer header). The warning against pasting it into shared chats or version-controlled files is exactly the kind of safety context an agent needs before echoing a credential.

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?

Two sentences: the first front-loads what the tool does and its auth status, the second delivers the only operational hazard (one-time secret) plus remediation. Nothing is redundant or buried.

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 one-optional-parameter write tool with no output schema, the description covers the essential behaviors: unauthenticated access, non-idempotency implied by "create," and the one-time secret return. It could note what else accompanies the secret (key id, name) but that omission is minor.

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?

The single `name` parameter already has 100% schema description coverage ("Label for the key, up to 80 characters"), and the description never mentions it. With schema coverage this high, the baseline of 3 applies since the schema carries the full parameter burden.

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 and resource ("Create a new Dagon account key") and even names the underlying endpoint (POST /v1/keys). No sibling in the list creates keys, so an agent can immediately route key-creation here rather than to balance, models, or chat tools.

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?

"No API key needed" tells the agent this is the bootstrap call usable before credentials exist, which is the key usage signal. It stops short of explicit when-not guidance or naming an alternative, but no plausible alternative exists among the siblings for minting credentials.

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

All Dagon Inference 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