Skip to main content
Glama
Sign In

RubiConnect

by com.rubiconnect.console
OverviewDiscussionsAdmin

get_template_detail

Retrieves the full content, folder placement, and configuration for a specific template by its name or ID.

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": {
      "templateIdentifier": "<templateIdentifier>"
    },
    "name": "get_template_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentIdNoUnique ID of the agent profile. If omitted, uses active agent from context.
accountIdNoOptional account ID (automatically scoped).
templateIdentifierYesThe name or unique ID of the template to retrieve.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses what data is returned (content, folder placement, configuration), and the verb 'Retrieves' implies a read operation, but it does not discuss permissions, error behavior for missing templates, or other operational details.

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 that communicates the core action, resource, and identifying input without any wasted words.

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 and no annotations, the description adequately lists the returned facets (full content, folder placement, configuration) so an agent can understand what it will receive. It could be slightly more complete by noting behavior when the template is not found, but it is sufficient for a retrieval tool.

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 all three parameters are already documented in the schema. The description reinforces that templateIdentifier accepts a name or ID, adding minor semantic value, but does not elaborate on agentId or accountId beyond what the schema provides.

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 ('Retrieves') with a clear resource ('template') and specifies the scope ('by its name or ID'). It implicitly distinguishes itself from list_templates by focusing on a single template, but it does not explicitly name sibling tools for differentiation.

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 this is the tool for getting details about a specific template when you have an identifier, but it offers no explicit when-to-use guidance, no alternatives for discovery (e.g., list_templates), and no exclusions.

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

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