Skip to main content
Glama

The project's logos

flypost_list_logos
Read-only

The project's logos as the editor's logo picker offers them: the default and any library logos (a white or brandmark version is just another entry), with the ids flypost_place_logo and flypost_carousel_logo take. Also the carousel logo settings from brand settings (show_logo, logo_scale).

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": "flypost_list_logos"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idNoProject id; omit for the active project.

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 cover the safety profile (readOnly, non-destructive, closed-world), so the description's job is return-shape disclosure, and it does that well: variants count as distinct entries, and the settings keys show_logo and logo_scale are surfaced. It does not mention ordering, completeness, or what happens when no logos exist, but that is a minor omission given the annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is one sentence with no filler, but it is a dense run-on that packs logos, variant semantics, two sibling tool references, and brand settings into a single clause with nested parentheses. The phrase 'with the ids flypost_place_logo and flypost_carousel_logo take' is grammatically garbled and slows parsing; splitting the settings disclosure into its own sentence would help.

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?

For a low-complexity read tool with one optional parameter at full schema coverage and no output schema, the description carries its share: it explains what the returned entries are and what extra settings ride along. Nothing essential for calling it correctly is missing, though an explicit 'read-only lookup, use before placing a logo' framing would close the loop.

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% and the single optional project_id is already documented as 'omit for the active project'. The description adds no scoping detail such as whether logos are project-specific or inherited, so it sits at the baseline for a fully documented single-parameter schema.

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 specifies the exact resource contents: the default plus library logos as the editor's logo picker exposes them, including that white/brandmark variants are separate entries, plus carousel logo settings. It stops short of a clean verb+resource statement ('list') and folds two payloads (logos and brand settings) into one phrase, but an agent can tell precisely what comes back.

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 naming flypost_place_logo and flypost_carousel_logo as the consumers of the returned ids, it hints this is the lookup to run before placing a logo, and that carousel settings are readable here. There is no explicit when-to-use, no when-not-to, and no statement of prerequisites.

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.