Skip to main content
Glama
Sign In

Convocore

by app.convocore.mcp
OverviewDiscussionsAdmin

import_agent

Import an agent from a template produced by export_agent / the OpenAPI export-template route. The template shape is complex; do not invent it manually unless the user provides an exact exported object.

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": {
      "agentTemplate": "<agentTemplate>",
      "agentName": "<agentName>"
    },
    "name": "import_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentNameYesName for the imported agent
fromAgentIdNoOptional source agent ID to preserve import lineage/context when the backend supports it.
agentTemplateYesAgent template object from export_agent / export-template. Pass the exported template object through; do not manually invent nested template fields.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive, non-idempotent, closed-world write, so safety profiling is covered. The description usefully adds that the template shape is complex and must be passed through verbatim, but says nothing about duplicate agent names, what happens on partial/failed imports, or the returned identifier.

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?

Two short sentences with zero filler, and the source-of-truth constraint (use an exported template, don't invent one) is front-loaded where an agent will see it.

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

Completeness3/5

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

For a mutation tool with a nested template object and no output schema, the description covers input provenance well but omits outcome information an agent needs to report success (returned agent ID, overwrite/duplicate behavior) and any differentiation from template-based sibling tools.

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 agentName, fromAgentId, and agentTemplate are already documented, including lineage for fromAgentId. The description only reinforces the template instruction, adding no new syntax or format detail beyond the schema, 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 and resource ('Import an agent from a template') and names the producing tool, export_agent. It does not, however, distinguish itself from the close siblings create_agent_from_template and clone_agent, so an agent could pick either for the same apparent intent.

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 the required context (you must have an object produced by export_agent) and adds a caution not to hand-build the template. It never says when to prefer this over create_agent_from_template or clone_agent, nor any prerequisite such as the target workspace or permissions.

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