Skip to main content
Glama

Look at my website

ver_mi_web
Read-onlyIdempotent

Use this when the person wants to know what is on one of their palimpalem websites before changing it. Requires palimpalem sign-in. Returns status, plan, the list of pages, languages, the last saved versions and an outline of one page with element ids (sections, titles, texts, photos), which editar_web can target. Read only.

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": {
      "web": "<web>"
    },
    "name": "ver_mi_web"
  }
}

Input Schema

NameRequiredDescriptionDefault
webYesThe website: its name (e.g. panaderia-ruzafa), its address (panaderia-ruzafa.palimpalem.com) or its own domain.
pageNoOptional. Which page to outline: its name from the page list (e.g. "menu") or its address. Without it, the home page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / page
      Added value: +{
      +  "description": "Optional. Which page to outline: its name from the page list (e.g. \"menu\") or its address. Without it, the home page.",
      +  "type": "string"
      +}
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, and the trailing 'Read only' mostly restates them. The genuinely additive part is the return profile — status, plan, page list, languages, last saved versions, and a single-page outline with element ids — plus the auth requirement, which no annotation conveys.

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?

Three sentences, front-loaded with the usage trigger and then the auth requirement and return contents. The dense enumeration of return fields is scannable, though the closing 'Read only' is redundant against the annotations and earns no place.

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 does the work of enumerating what comes back and how the page parameter scopes the outline, which is enough to call it correctly. Nothing is said about size or cost of the outline for large pages, but that is a minor omission for a read-only inspection tool.

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 coverage is 100% and both parameters carry examples and defaults, so the baseline is 3. The description only indirectly clarifies parameter meaning by explaining that the outline covers 'one page' and its element ids, which an agent could already infer from the page parameter's own description.

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?

States a specific verb and resource ('know what is on one of their palimpalem websites') and explicitly frames it as the read-side counterpart to editar_web. It is clear what the tool does, though it does not distinguish itself from lookalike siblings that also surface site state, such as estado_web or versiones_web.

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

Usage Guidelines4/5

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

Gives an explicit trigger — the person wants to inspect a site before changing it — plus the prerequisite of a palimpalem sign-in and the follow-on action (editar_web targeting the element ids). No exclusion clause exists, so an agent must still infer when a different inspection tool is preferable.

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.