Skip to main content
Glama

View Brand Files

view_files
Read-onlyIdempotent

View brand text, images, and font files. Returns each file's text content or link, or a per-file error. Viewing a font file also returns its font specimen, when one exists.

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": {
      "brand_session_id": "<brand_session_id>",
      "files": "<files>"
    },
    "name": "view_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYesFiles to read by exact path from get_brand.files. Each line_range uses one-based, inclusive start and end lines; start must be less than or equal to end.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.
version_idNoVersion ID from get_brand or list_brand_versions identifying the snapshot whose files to read. Omit to use the latest version.
brand_session_idYesBrand session ID from `get_brand`.

Output Schema

NameRequiredDescriptionDefault
resultsYesOne result per requested path, in request order. A failed file read does not prevent other files from being returned.
version_idYesImmutable version used for every file in this response.
brand_session_idYesBrand whose files were read.
message_for_assistantNoContext, explanations, or actionable guidance for the calling assistant. Hosts may display it, but it is not copy that must be shown to the user verbatim.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral detail beyond that: results are per-file, each entry yields text content or a link, a per-file error is possible without failing the whole call, and font files may include a specimen. Only the partial-failure nuance could be stated more explicitly.

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?

Three short sentences, front-loaded with the core action and resource, then the return shape, then the font-specimen exception. No filler and no repetition of schema content.

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?

An output schema exists and the description still usefully previews return shape, and all four parameters are fully documented in-schema, so an agent can call this correctly. The one gap is usage context — when to prefer this over the edit-file or brand-lookup siblings — which is not covered anywhere in the description.

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%, with path, line_range, version_id, and llm_model all documented in-schema, including the one-based inclusive semantics and the get_brand.files provenance. The description adds no parameter meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

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 names a specific verb and resource (view brand text, images, and font files) and states what comes back for each file, so an agent knows this is a read-by-path tool rather than a listing or edit tool. It stops short of naming the sibling that supplies the paths (get_brand) or contrasting with get_brand_edit_file, so differentiation is implied rather than stated.

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 contains no when-to-use guidance, no prerequisites, and no alternatives. The workflow hint ('Files to read by exact path from get_brand.files') lives only in the input schema, so an agent reading the description alone gets no routing information.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources