Skip to main content
Glama
Sign In

PixelGlass

by co.pixelglass
OverviewDiscussionsAdmin

Get the navigation

get_navigation
Read-onlyDestructive

On one site of the account, named in site. The site's two menus, as Settings › Design › Navigation shows them: navigation, the masthead's (Primary), and secondary_navigation, the footer's (Secondary), each an ordered list of { label, url }. Beside them, what a row can link to: the site's shortcuts (the member doors only while members are on), its published pages, its collections and its site pages. Themes read the menus as site.navigation and site.secondary_navigation.

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": {
      "site": "<site>"
    },
    "name": "get_navigation"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site to work on, as list_sites names it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior1/5

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

The description describes a read-only retrieval of navigation data, but the annotations declare destructiveHint=true and idempotentHint=false for a tool named and described as 'Get'. This contradicts the get semantics, so the behavioral-transparency score is capped at 1 despite the otherwise useful return-content detail.

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?

The description is information-dense and front-loads the site scope, but it is awkwardly structured with fragments and the 'Beside them, what a row can link to' construction. It conveys useful details, but the wording could be considerably tighter and clearer.

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?

With no output schema, the description carries the return shape: two menus, ordered label/url entries, linkable shortcuts/pages/collections/site pages, the member-doors caveat, and theme variable names. This is fairly complete for a read-only navigation getter, though it could more explicitly frame the operation as non-destructive.

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 schema already states that site must be named as list_sites names it. The description repeats 'named in site' but adds no syntax or format details beyond the schema, so the baseline of 3 applies.

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 identifies the resource precisely: one site's two menus (Primary masthead and Secondary footer), each as an ordered list of label/url, plus the linkable targets. It is distinguishable from set_navigation by content, but it opens with a sentence fragment and never uses a retrieval verb, so the action 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?

There is no explicit when-to-use or when-not guidance. The description gives context about Settings › Design › Navigation and theme access, but it never routes the agent to set_navigation for edits or explains when to prefer another sibling.

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

All PixelGlass toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources