Skip to main content
Glama
Sign In

Convocore

by app.convocore.mcp
OverviewDiscussionsAdmin

orgs_write

Destructive

Create/update/delete organizations or assign/unassign an agent to an org. Actions: create, update, delete, assign_agent. For reads use orgs_write siblings orgs_read. Destructive: delete removes the org and associated clients.

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": {
      "action": "<action>"
    },
    "name": "orgs_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgNoFor action=update: org fields to change (from the main org schema; only what you send changes).
nameNoFor create: org display name (Clients page card).
emailNoFor create: org contact email.
orgIdNoOrg id (orgs_read list / search). Required for update, delete and assign_agent.
actionYes
agentIdNoFor assign_agent: the agent to give to (or take from) the org.
assignActionNoFor assign_agent: assign gives the org access to the agent, unassign removes it.
squarePhotoURLNoFor create: org logo URL (https), shown as a round avatar.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructive=true and idempotent=false, and the description earns credit for disclosing the consequence beyond the hint: delete removes the org AND associated clients. It doesn't note whether update is a partial merge (schema hints at it) or any permission requirements.

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?

Three front-loaded sentences with no filler, and the destructive warning is placed prominently. The phrase 'For reads use orgs_write siblings orgs_read' is slightly awkward/typo-laden, marginally hurting polish.

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 multi-action mutation with nested objects, destructive scope, and no output schema, the description covers the action set and the key hazard. Minor gaps: no mention of update partial-merge behavior (deferred to schema) and no note on assign prerequisites.

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 88%, so the schema already documents nearly all params, including action, orgId, agentId, and assignAction. The description adds only the action list and no syntax or format detail beyond structured fields, matching the baseline 3.

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?

Uses specific verbs and resource ('Create/update/delete organizations', 'assign/unassign an agent') and enumerates the four action values, so an agent knows exactly what it can do. It also explicitly excludes the read side by naming orgs_read.

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?

Clear routing for reads to orgs_read and per-action intent is stated in the schema; the description gives a solid when-to-use context. It stops short of naming the overlapping clients_write sibling or stating per-action prerequisites, so not a full 5.

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

All Convocore 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