Skip to main content
Glama
Sign In

Yuppsy

by com.yuppsy
OverviewDiscussionsAdmin

website_agent_create

Creates Agent website for the specified agent id. See website_create for more details.

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": {
      "data": "<data>"
    },
    "name": "website_agent_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesThe agent website data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / data / description
      Added value: +"The agent website data."
  2. Changed3 schema fields changed
    • removedInput schema / properties / data / properties / type
      Removed value: -{
-  "description": "Type of website: Agent, Property",
-  "enum": [
-    "None",
-    "Agent",
-    "Property"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / data / properties / typeId
      Removed value: -{
-  "description": "The id of the data the website is based on: AgentId, PropertyId",
-  "type": "integer"
-}
    • addedInput schema / properties / data / required
      Added value: +[
+  "agentId"
+]
  3. Changed6 schema fields changed
    • addedInput schema / properties / data / properties / agentId / description
      Added value: +"Agent id"
    • addedInput schema / properties / data / properties / domain / description
      Added value: +"The domain of the website (e.g., example.com), if any. Not required."
    • addedInput schema / properties / data / properties / subdomain / description
      Added value: +"You can set a custom subdomain for the website (e.g., mycustomsubdomain.example.com). If UseTypeNameAsSubdomain is true, this property will be ignored."
    • addedInput schema / properties / data / properties / type / description
      Added value: +"Type of website: Agent, Property"
    • addedInput schema / properties / data / properties / typeId / description
      Added value: +"The id of the data the website is based on: AgentId, PropertyId"
    • addedInput schema / properties / data / properties / useTypeNameAsSubdomain / description
      Added value: +"Set to true if the website should use the type name as a subdomain (e.g., agent.example.com, property.example.com). If false, the Subdomain property will be used instead."
  4. Added

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not say whether the created site goes live (despite website_agent_publish and website_agent_set_live siblings implying it does not), whether a domain/subdomain must be free, what permissions are needed, or what is returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, but the second sentence spends its words pointing to another tool rather than explaining this one. Every sentence should earn its place; the cross-reference does not.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutating tool with a nested payload, no annotations, and no output schema, the description should at least state the resulting state (draft vs live) and return shape. It omits both, leaving the agent to infer behavior from sibling names like website_agent_publish.

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 description coverage is 100%, and the nested object documents domain, subdomain, and useTypeNameAsSubdomain with examples, so the schema already does the heavy lifting. The description adds nothing about the interplay between subdomain and useTypeNameAsSubdomain, so 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?

The description names a specific verb and resource ('Creates Agent website') plus the required key ('specified agent id'), so the operation is identifiable at a glance. It does not explain how this differs from the near-named siblings website_create or website_property_create beyond the word 'Agent'.

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

Usage Guidelines2/5

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

There is no statement of when to choose this over website_create, website_property_create, or subscription_set_agent_website_to_first_available. The only routing hint is 'See website_create for more details', which defers rather than guiding, and gives no exclusions or prerequisites.

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

All Yuppsy 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