Skip to main content
Glama
Sign In
Box MCP Server

Box MCP Server

by yandisa2005
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

box_docgen_template_get_by_name_tool

Retrieve metadata for a specific Box Doc Gen template by name to identify and inspect its details before generating documents.

Instructions

Retrieve details of a specific Box Doc Gen template by name.

Args: client (BoxClient): Authenticated Box client. template_name (str): Name of the template.

Returns: dict[str, Any]: Metadata of the template or an error message.

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": {
      "template_name": "<template_name>"
    },
    "name": "box_docgen_template_get_by_name_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
template_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a retrieval operation (implying read-only) and mentions it returns metadata or an error message, but lacks details about authentication requirements, rate limits, error conditions, or what specific metadata is included. For a tool with zero annotation coverage, this is insufficient.

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?

The description is well-structured with clear sections (purpose, args, returns) and uses minimal words to convey essential information. Every sentence serves a purpose, though the 'Args' and 'Returns' sections could be integrated more seamlessly into natural language.

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?

Given the tool has an output schema (which handles return values), no annotations, and a simple parameter structure, the description is moderately complete. It covers the basic operation and parameter, but lacks behavioral context and usage guidance that would be helpful for an AI agent, especially since annotations are absent.

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 0%, so the description must compensate. It documents the single parameter 'template_name' and its purpose ('Name of the template'), which adds meaningful context beyond the bare schema. However, it doesn't provide format expectations, constraints, or examples for the template name parameter.

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 clearly states the verb ('Retrieve details') and resource ('specific Box Doc Gen template by name'), making the purpose unambiguous. It distinguishes from siblings like 'box_docgen_template_get_by_id_tool' by specifying retrieval by name rather than ID, though it doesn't explicitly contrast with all sibling tools.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention when to prefer this over 'box_docgen_template_get_by_id_tool' or 'box_docgen_template_list_tool', nor does it discuss prerequisites like authentication or template existence.

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

Deploy Server

Other Tools