Skip to main content
Glama

Set the agency footer credit

set_footer_credit
Idempotent

Show, hide or customise the agency footer credit ("Made with ♥ by …") on one site. "hide" removes it on this site, "show" displays it (optionally with custom text — "{heart}" renders a heart — and url), "reset" returns to the agency-wide default. Only agency staff can change it; an end client with site access is refused.

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_id": "<site_id>",
      "action": "<action>"
    },
    "name": "set_footer_credit"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoFor "show": custom https link. Omit to use the agency default.
textNoFor "show": custom credit text. Omit to use the agency default.
actionYes"show", "hide" or "reset"
site_idYesThe site, from list_sites
user_goalNoOptional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_goal
      Added value: +{
      +  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (non-read-only, idempotent, non-destructive). The description adds real value beyond that: the permission boundary ('Only agency staff can change it; an end client with site access is refused') and the effect of reset. It leaves one gap: whether a 'show' without text/url preserves or clears an existing custom credit.

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 tight paragraph that front-loads the purpose, then enumerates actions, then the permission constraint. Every clause carries information; nothing is padding.

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?

Covers actions, permissions, and the placeholder token — everything needed to invoke it correctly for a 5-parameter mutation tool with no output schema. The only omission is what happens to existing custom text/url when 'show' is called without them.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning the schema does not: the '{heart}' placeholder rendering, and the pairing of text/url with the 'show' action. It does not explain the user_goal parameter, though the schema handles that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb set (show/hide/customise) and a concrete resource (agency footer credit) with the exact rendered form 'Made with ♥ by …'. This is clearly distinct from neighbouring tools like update_site_settings or set_runtime_text.

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?

Explicitly defines when each action applies: 'hide' removes it on this site, 'show' displays it, 'reset' returns to the agency-wide default. Also states who may use it. It does not name an alternative tool for site-wide settings, but the action semantics leave little ambiguity.

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.

Resources