Skip to main content
Glama
Offorte Proposal Software

Offorte Proposal Software

Official
by offorte

get_text_templates

Read-only

Lists available language text templates for creating new proposals, helping you select the right template before generating a proposal.

Instructions

Lists available language text templates which are used to create new proposals

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_text_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.1
  2. Removed
  3. Changed2 schema fields changedv1.0.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  4. 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 readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only that these templates feed proposal creation; it says nothing about pagination, ordering, language coverage, or whether the list is tenant-scoped.

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?

A single, front-loaded sentence with no filler. It is hard to trim further, though the subclause about proposal creation could be the leading clause if usage were the priority.

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?

This is a simple zero-parameter read tool, so the bar is low, but with no output schema the description does not tell the agent what the list entries contain (IDs, language codes, text bodies) or how to use them in a subsequent create_proposal call. That missing link is what an agent most needs here.

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?

The tool takes zero parameters, so there is no parameter meaning to convey; baseline for parameterless tools applies. Nothing in the description contradicts or misleads about inputs.

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?

Specific verb plus resource ('Lists available language text templates') with added scope explaining what the templates are for ('used to create new proposals'). It partially distinguishes from siblings like get_proposal_templates and get_email_templates, though the boundary between 'language text templates' and 'proposal templates' is not made explicit.

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?

Usage is only implied by the phrase 'used to create new proposals', giving a loose hint about when an agent would want this list. There is no explicit statement of when to prefer this over get_proposal_templates, get_design_templates, or get_email_templates.

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