Skip to main content
Glama

Find templates

find_templates
Read-onlyIdempotent

Search all available connections for Word, PowerPoint, or Excel templates by format and name substring, returning best matches with location and source so you can open or create documents.

Instructions

Find templates in every connection that has a template location: an organization library, a workgroup or personal Office templates folder, or a templates folder in a connection. format is word, powerpoint, excel, or "" for all; nameContains keeps names containing it, ignoring case. Returns {templates: [{connectionId, source, name, folder, format, location}], connectionsSearched, connectionsFailed: [{connectionId, code, message}]}, best match first; location is organization, workgroup, personal or connection. Pass connectionId and source to open_document, or as create_document's template source.

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": {
      "format": "<format>",
      "nameContains": "<nameContains>",
      "maximumResults": "<maximumResults>"
    },
    "name": "find_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatYes
nameContainsYes
maximumResultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description goes well beyond that by disclosing the return payload shape, the best-match-first ordering, and the presence of a connectionsFailed array with code/message per failed connection — behavior an agent could not infer from annotations.

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 content is front-loaded and dense, with no filler sentences — every clause carries information about locations, parameters, return shape, or downstream use. It is a single long run-on sentence chain stitched with semicolons, which slightly hurts scanability but not meaning.

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

Completeness5/5

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

There is no output schema, and the description compensates fully by spelling out the returned object fields and error reporting. Combined with the four enumerated location values and the downstream hand-off instructions, an agent has everything needed to call and use results correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 carry parameter meaning, and it does for two of three: format is enumerated (word, powerpoint, excel, or empty string for all) and nameContains is defined as a case-insensitive substring filter. maximumResults, despite being required, is never mentioned, leaving one parameter entirely undocumented.

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?

The description opens with a specific verb and resource ("Find templates") and immediately scopes it to "every connection that has a template location," then enumerates the four possible locations. This clearly separates it from sibling search/listing tools like list_documents and find_in_document.

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?

It explains the conditions under which templates exist (organization library, workgroup or personal folder, connection templates folder) and tells the agent what to do with results: pass connectionId and source to open_document or as create_document's template source. It lacks an explicit statement of when NOT to use this tool versus a document search, but the surrounding context makes the intent clear.

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