Skip to main content
Glama
Sign In

Total CMS

by co.totalcms
OverviewDiscussions(1)Admin

get_view

Read-onlyIdempotent

Fetch a data view's full cached result by id. Output is freeform — each item's field set depends on the view's Twig definition. Call describe_view first to learn the expected shape. Capped at 50 items; larger views return the first 50 plus a hint to call query_view for pagination. For per-item paginated access use query_view directly.

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": {
      "id": "<id>"
    },
    "name": "get_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesView id. Use list_views to discover available views.
formatNoForward-compat with collection tools. View data is freeform so this has no effect today.markdown
localeNoBCP 47 locale tag — forward-compat for the 3.6 i18n release. No effect today.

Output Schema

NameRequiredDescriptionDefault
hintNoPresent only when truncated — points the agent at query_view.
itemsYesItems produced by the view, capped at 50. Field set varies by view — call describe_view for the expected shape.
totalYesTotal cached items in the view (pre-cap).
truncatedYesTrue when total > 50; pair with query_view for full pagination.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well past the annotations (which only declare read-only/idempotent safety) by disclosing that output is freeform and shape-dependent on the Twig definition, and by disclosing the hard 50-item cap plus the truncation hint. Those are exactly the behaviors an agent needs and cannot infer from structured fields.

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?

Four tight sentences, each doing distinct work: purpose, output shape, prerequisite, and truncation/routing. The cap and the fallback to query_view are front-loaded before any incidental detail.

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?

Although an output schema exists, the description correctly warns that the return shape is effectively freeform and view-dependent, plus it covers truncation and the prerequisite call. Nothing an agent needs to invoke this correctly is missing.

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 the baseline is 3; the description confirms the 'by id' lookup but adds no syntax or format guidance for params. The schema itself already documents format and locale as no-effect forward-compat fields, so the description's silence is acceptable but not additive.

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?

States a specific verb and resource: 'Fetch a data view's full cached result by id'. The 'full cached result' phrasing contrasts with the per-item paginated access of query_view, so the agent can separate the two siblings without reading schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit sequencing ('Call describe_view first to learn the expected shape') and an explicit alternative with its selecting condition ('For per-item paginated access use query_view directly'). Both when-to-use and when-to-use-something-else are covered.

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

All Total CMS toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources