Skip to main content
Glama

HeyIdentity

add_client

Adds a client. client: { client_id, client_secret?, allow_all_return_urls?, redirect_uris?, allowed_scopes?, exposed_scopes?, access_token_audience? }.

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": {
      "configuration_id": "<configuration_id>",
      "client": "<client>"
    },
    "name": "add_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientYesThe client, as in the Agent API. A client (an app that signs in, or an API). On edit, fields left out keep their value.
configuration_idYesThe configuration id (from create_tenant or get_tenant).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only restates the resource and field list. It says nothing about whether client_id must be unique, what happens on conflict, whether the client is immediately active, required permissions, or which defaults apply — details that do appear in the schema but not here.

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 short sentences, front-loaded with the operation, with no filler. The field list is largely redundant with the schema, which costs it a point but does provide a quick summary of the nested payload.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the definition is thin — it does not disclose error behavior, uniqueness constraints, defaults, or what is returned after creation. The rich schema covers parameter detail, but the description does not compensate for the missing behavioral and usage context.

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 explains client_id, client_secret validation, redirect URI formats, scope defaults, and audience rules in depth. The description's field enumeration duplicates the schema without adding syntax, defaults, or edge-case meaning, which matches the baseline of 3 for high-coverage schemas.

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?

The description uses a specific verb and resource ("Adds a client") and names the nested object's fields, so an agent knows exactly what resource is being created. It stops short of differentiating itself from obvious siblings such as edit_client or add_user, so it does not reach the top band.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites (e.g. that a configuration must exist first), and no reference to alternatives like edit_client for modifying an existing client. An agent must infer the create-vs-edit boundary entirely from the tool name.

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.

Resources