Omnara

Create agent profile

profiles_create

Creates a named profile that points at an agent config and returns the profile with its current config.

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": {
      "config": "<config>",
      "name": "<name>",
      "orgID": "<orgID>",
      "projectID": "<projectID>"
    },
    "name": "profiles_create"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Human-readable name. Spaces and punctuation are allowed; leading or trailing whitespace and invisible or control characters are not.
`orgID`	Yes	Organization ID (org_...).
`config`	Yes	Agent config ID (acfg_...).
`projectID`	Yes	Project ID (proj_...).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 17, 2026
- addedInput schema / properties / config / description
```
Added value: +"Agent config ID (acfg_...)."
```
- addedInput schema / properties / orgID / description
```
Added value: +"Organization ID (org_...)."
```
- addedInput schema / properties / projectID / description
```
Added value: +"Project ID (proj_...)."
```
First observedOct 13, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the mutation profile is covered. The description usefully adds that the created profile is returned with its current config, but it does not disclose the consequence of idempotentHint=false (e.g., whether duplicate names are allowed) or any auth/error behavior.

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?

A single front-loaded sentence with no filler. It conveys the action, the entity, its link to a config, and the return value without redundancy.

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 no output schema, the description correctly notes what is returned, which an agent needs. It falls short only on creation-time edge cases (name uniqueness, duplicate handling, failure modes) for a non-idempotent create.

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%: each of the four parameters has format details (org_, acfg_, proj_ patterns) documented in the schema. The description only restates that the profile 'points at an agent config' and is 'named', adding no semantics beyond what the schema already supplies, so the baseline 3 applies.

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?

States a specific verb (creates) and resource (named profile) and clarifies the linkage to an agent config. It does not explicitly contrast itself with siblings like profiles_update or profiles_rename, but 'create' is unambiguous enough that an agent can distinguish it from the other profile operations.

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?

The description never says when to use this tool versus profiles_update, profiles_rename, or profiles_get, nor does it state prerequisites such as needing an existing agent config ID. The only implicit guidance is the word 'Creates'.

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

All Omnara tools Inspect

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.