Skip to main content
Glama

Show the state of my website

estado_web
Read-onlyIdempotent

Use this when the person asks how their palimpalem website stands overall: online or not, free or Plus and until when, own domain and until when, e-mail package, pages and languages. Requires palimpalem sign-in. Read only.

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

Input Schema

NameRequiredDescriptionDefault
webNoOptional when the account has one website. Its name, palimpalem address or own domain.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so 'Read only' is largely redundant. The description does add real value beyond the structured fields: it discloses the sign-in requirement ('Requires palimpalem sign-in') and previews exactly which state facets are returned, which annotations cannot convey.

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?

Compact and front-loaded: the usage trigger comes first, followed by the enumerated state list and then auth/read-only constraints. Every clause carries information; the only near-waste is 'Read only', which the annotations already state.

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 usefully previews the returned facets (plan and expiry, domain and expiry, e-mail, pages, languages) and discloses the auth prerequisite. Combined with the fully documented single parameter and read-only annotations, an agent has what it needs to call this correctly, though multi-site disambiguation could be spelled out more.

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?

There is a single optional parameter with 100% schema description coverage, so the schema fully explains that 'web' accepts a name, palimpalem address or own domain and is optional when the account has one website. The description does not mention the parameter at all, so it adds nothing beyond the schema; baseline 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?

States a specific verb ('asks how their website stands') and resource (palimpalem website), then enumerates the state dimensions reported: online status, free vs Plus with expiry, own domain with expiry, e-mail package, pages and languages. This enumeration distinguishes it from single-facet siblings like comprobar_dominio or idiomas_web, though no sibling is named explicitly.

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 condition: 'Use this when the person asks how their palimpalem website stands overall.' The word 'overall' implicitly steers narrow questions toward narrower tools, but no alternatives or when-not conditions are named, so guidance is clear but not exhaustive.

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.