Skip to main content
Glama

osirAgentConfigure

Idempotent

osirAgentConfigure: Connect the user's AI agent (e.g. Hermes) to a model provider - 'connect my Hermes to DeepSeek'. Providers: deepseek, openai, openrouter, anthropic. The API key is stored as an encrypted secret, never written into a file or shown again, and the agent restarts on the user's VPS with it. Never paste the key anywhere else. Requires authentication.

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": {
      "agentId": "<agentId>",
      "provider": "<provider>",
      "apiKey": "<apiKey>"
    },
    "name": "osirAgentConfigure"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyYesThe user's API key for that provider. Never logged or returned.
agentIdYesAgent id from osirAgentList or osirAgentDeploy.
providerYesModel provider: 'deepseek', 'openai', 'openrouter' or 'anthropic'.
sessionKeyNoSession key (osk_...) returned by checkDeviceLoginStatus. Pass it on every call when logged in via the in-chat device flow; omit when connected via OAuth.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, idempotentHint=true and destructiveHint=false. The description goes well beyond that: the API key is stored as an encrypted secret, never written to a file, never shown again, and the agent restarts on the user's VPS as a side effect. Those are exactly the consequences an agent needs before performing a credential-bearing mutation.

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 purpose and the example utterance are front-loaded, and the safety warning follows immediately. There is minor redundancy with the schema (the provider enumeration appears twice) and the 'Never paste the key anywhere else' line is an instruction rather than a definition, but nothing is bloated.

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 4-parameter mutation with annotations and no output schema, the description covers purpose, credential handling, the restart side effect and the auth prerequisite. It stops short of describing failure behavior (invalid key, unreachable VPS) or the sessionKey path, which an agent would need to recover from errors.

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 baseline is 3, and the description's provider list and key-handling note largely restate what the schema already documents for 'provider' and 'apiKey'. The sessionKey parameter and its device-flow-vs-OAuth condition are not mentioned in the description at all, so it adds little beyond the structured fields.

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 verb and resource ('Connect the user's AI agent ... to a model provider') and anchors it to a real user utterance ('connect my Hermes to DeepSeek'), then enumerates the supported providers. This is clearly distinguishable from sibling lifecycle tools like osirAgentDeploy or osirAgentList, which handle deployment and enumeration rather than provider wiring.

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?

It gives a concrete trigger phrase and the constraint 'Requires authentication', so an agent knows the context in which to reach for it. It does not explicitly state when-not-to-use or point to a sibling alternative (e.g. what to call if the agent isn't deployed yet), leaving a small gap.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.