Skip to main content
Glama
Sign In

SameDayDesk agent tools

by com.samedaydesk
OverviewDiscussionsAdmin

generate_complete_fix_pack

Read-onlyIdempotent

PAID. Returns the complete, ready-to-paste AI-readiness Fix Pack for a site: tailored Organization + FAQPage JSON-LD, an AI-crawler robots.txt, a sitemap, and title/meta/Open Graph fixes. Requires a license — the checkout-session id you receive after buying the $39 Fix Pack at https://buy.stripe.com/8x24gA0xA9DF9dd13YeZ20h (after paying you're shown your license code). Without a valid license it returns purchase instructions plus a free starter pack.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe website to generate the Fix Pack for.
licenseNoYour Stripe checkout-session license code (starts with cs_).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations cover safety (readOnly, idempotent, non-destructive), and the description adds what annotations cannot: a paywall, an auth credential requirement, and a documented fallback response when the license is absent. It stops short of describing rate limits or the exact form of the returned pack (inline text vs. downloadable files).

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?

Front-loads the critical qualifier ('PAID.') and the deliverable list before the license mechanics. Efficient overall, though the long Stripe URL and parenthetical add some weight to an otherwise tight paragraph.

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-value burden and largely does so: it lists what the pack contains and what is returned without a valid license. The one remaining ambiguity is the delivery format of the pack, but nothing needed to invoke the tool correctly is missing.

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%, so both parameters are already documented, including the cs_ prefix for `license`. The description reinforces the license's origin (Stripe checkout-session id) and the consequence of an invalid value, which is useful but does not add syntax or format detail beyond the schema.

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?

Names a specific verb (generate) and resource (complete AI-readiness Fix Pack) and enumerates the concrete deliverables: Organization + FAQPage JSON-LD, AI-crawler robots.txt, sitemap, title/meta/Open Graph fixes. This is clearly distinct from the diagnostic siblings like check_ai_readiness and check_agent_readiness.

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?

States the gating condition explicitly (requires a `license`, obtainable after the $39 Stripe purchase) and the alternate behavior without one (returns purchase instructions plus a free starter pack). It does not name a sibling to use for the free/diagnostic path, so routing is implied rather than explicit.

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

All SameDayDesk agent tools 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