Skip to main content
Glama
Sign In

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Create page

create_page

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": {
      "name": "<name>",
      "code": "<code>"
    },
    "name": "create_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe page's whole code: React JSX defining `function Page()`, as the guide describes.
nameYesThe page's name in the Pages list, e.g. "Accounts".
change_noteNoWhat this first version does, shown in the page's history.
descriptionNoOne line saying what the page is for, shown under its name.
on_behalf_ofNoA teammate's email, or an agency client's from list_agency_clients, to run this call in that account: their agents, settings, connected accounts, and credits. Omit it to act on your own account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / on_behalf_of / description
      Previous value: -"An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."New value: +"A teammate's email, or an agency client's from list_agency_clients, to run this call in that account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already mark this as a non-read-only, non-destructive write, so the description doesn't need to restate that. It instead adds real behavioral context the annotations lack: the mandatory skill-guide read before writing code, and the post-call requirement to return the actual `url` rather than a placeholder. It stops short of covering failure modes or what happens if `code` is invalid.

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?

The summary is front-loaded with the substance — what a page is — followed by the prerequisite and the output instruction, with no filler. The parenthetical data-source list is a little dense but each clause carries information.

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 five-parameter write tool with no output schema, the description covers what the page is, what preparation is required, and how to report the result, and a `<returns>` block identifies the shape as the list_pages row. It leaves the authoring contract to the referenced skill guide, which is a reasonable delegation rather than a gap.

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 the baseline is 3, but the description earns above that by explaining how `code` must be produced (React JSX defining `function Page()`, per the guide) and by tying the response to the `url` field on the returned list_pages row. No parameter meanings are contradicted or left ambiguous.

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 concrete verb and resource ('Build a custom page') and defines what the artifact is: a team-visible view over people, companies, outreach, deals and to-dos, used as a tracker, dashboard or report. That scope is specific enough to separate it from update_page, get_page and list_pages on the sibling list without opening a schema.

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 a clear prerequisite chain: load the `pages` skill guide with get_skill_guide before writing `code`, then surface the resulting `url` to the user. It does not explicitly say when to prefer create_page over update_page for an existing page, though the 'first version' language in change_note hints at it.

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

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