Omnara

Rename agent profile

profiles_rename

Destructive

Renames an agent profile without changing its config. Agents and cron triggers reference the profile by ID and keep working, but configs that name the profile under subagents must use the new name the next time they're compiled.

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

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_...).
`projectID`	Yes	Project ID (proj_...).
`agentProfileID`	Yes	Agent profile ID (aprf_...).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 17, 2026
- addedInput schema / properties / agentProfileID / description
```
Added value: +"Agent profile ID (aprf_...)."
```
- 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

A4/5.0

Behavior4/5

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

Annotations flag destructiveHint=true and idempotentHint=false but say nothing about referential consequences. The description adds real behavioral context beyond the annotations: agents and cron triggers reference by ID and survive the rename, while configs naming the profile under subagents must be recompiled. That non-obvious downstream effect is exactly what the agent needs, though permissions/rollback are unaddressed.

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?

One sentence, front-loaded with the core action and config-preservation guarantee, followed by the downstream referential behavior. Every clause earns its place with no 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?

For a 4-param mutation with full schema coverage and no output schema, the description supplies the missing behavioral dimension (what happens to references) and stays concise. It could note whether the old name is reserved or whether duplicate names are rejected, but the essential call-time context is present.

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 documents all four parameters including the NFC normalization and whitespace constraints on name. The description adds no parameter-level detail beyond that, which is the expected baseline when the schema carries the load.

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?

Specific verb+resource ('Renames an agent profile') with an immediate scoping clause ('without changing its config') that distinguishes it from profiles_update. An agent can differentiate this from the sibling profiles_update without opening either schema.

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?

The description implies when to use it (name change only, not config change) by contrasting with config mutation, which is useful implied guidance. However, it never explicitly names an alternative like profiles_update or states when not to use this tool, so an agent must infer the routing.

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.