Guest Logic Hotel PMS

Set the logo

set_logo

Sets the company's logo from a public web address (PNG, JPEG or WebP, up to 10 MB). Needs the owner's sign-in.

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": {
      "url": "<url>"
    },
    "name": "set_logo"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Public https address of the logo

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world operation, and the description adds real substance beyond that: accepted formats (PNG, JPEG, WebP), a 10 MB size ceiling, and the owner-level authorization requirement. It stops short of saying whether an existing logo is replaced or retained, which is the main behavioral unknown for a 'set' operation.

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?

A single sentence with the action and source front-loaded and constraints packed into one parenthetical. Every clause carries information an agent needs; nothing is redundant with the title or annotations.

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 one-parameter tool with full schema coverage and no output schema, the description supplies the auth, format and size facts an agent needs to call it successfully. The only notable omission is the effect on a pre-existing logo, which is minor given the tool's simplicity.

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 the url property is documented as a public https address, so the baseline is 3. The description contributes additional constraint meaning for that parameter — accepted MIME types and the 10 MB limit — but not format syntax or validation details beyond it.

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 ('Sets the company's logo') plus the source of the asset ('from a public web address'), so an agent can identify the operation immediately. It does not explicitly differentiate itself from plausible siblings such as add_photo or upload_file, leaving that boundary to inference.

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 implied rather than stated: the agent can infer this is for company branding when a logo URL is available, and the 'Needs the owner's sign-in' clause supplies a prerequisite. There is no when-not guidance and no pointer to add_photo/upload_file for image-adjacent tasks.

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

All Guest Logic Hotel PMS tools Inspect

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

Need Help?