Skip to main content
Glama

Galley Render

by com.galleyrender
OverviewDiscussionsAdmin

Create an account and get an API key

create_account
Idempotent

Turn the keyless trial into a real account and get a permanent API key.

Call it once with an email. A link is mailed to that address and the tool returns status: "pending_verification" with a four-character request_code. Tell the person the code. The link opens a page that names who asked, when, and the code, and nothing happens until the person answers it: they confirm the request only if it shows the code you gave them. After they confirm, call this again with the same email, from this same client, and it returns the API key, once. The key goes only to the client whose request was confirmed, and that client is then bound to the account, so a connector that cannot send headers is connected from then on.

A client with no identity of its own can't be handed the key (can_receive_key: false). That is any client that sent no key and no client id — every hosted connector added with the shared URL, because they all call from their vendor's servers. Its person verifies the address on the page and sees the key there, once. To use the account from such a connector afterwards, add it with a personal URL (https://mcp.galleyrender.com/mcp/c/<id>).

If the person says the request wasn't theirs, it is cancelled, this returns status: "declined", and the address can't be asked about again from this client for a day.

If that address already has an account, no second one is made, and no key comes back. You get status: "existing_account", verified: false, existing_account: true, and a one-time code in the post — hand that code to link_account and this client is connected to the account that already exists. Use this rather than inventing a second address: two accounts means two free tiers and two sets of templates, and the renders anyone is waiting for are on the first one. A key on the connection changes this only if it is a live key for that same account.

When the person confirms this client's request, this client's trial is upgraded in place, so templates and renders made during the trial are kept. The free tier is 5 PDF pages or 5 images a month; Solo is $5 a month for 200 PDF pages or 500 images. Pricing: https://galleyrender.com/pricing. Store the key as a secret — it is shown only on that one call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoAccount name. Defaults to the local part of the email.
emailYesWhere to send the verification link. Use the address of the person who owns this project — not a made-up one; the key is only released after the link is clicked. If this address already has a Galley account, no second one is made: a one-time link code is mailed to it instead, and `link_account` takes that code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / email / description
      Previous value: -"Where to send the verification link. Use the address of the person who owns this project — not a made-up one; the key is only released after the link is clicked."New value: +"Where to send the verification link. Use the address of the person who owns this project — not a made-up one; the key is only released after the link is clicked. If this address already has a Galley account, no second one is made: a one-time link code is mailed to it instead, and `link_account` takes that code."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The description richly discloses behaviors beyond the annotations: a verification email is sent, the key is returned only once, the client becomes bound to the account, no second account is created for existing addresses, and trial data is preserved. It explains security constraints and side effects thoroughly without contradicting the provided annotations.

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 description is long, but it earns its length by covering a complex two-phase flow, edge cases, statuses, and security rules. It is front-loaded with the core purpose and uses formatting like bold warnings and status names effectively. Some redundancy exists around the existing-account scenario, and the pricing sentence is tangential, but overall it is well organized.

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

Completeness5/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 fully compensates by explaining every possible return status, the confirmation flow, what happens when the request is declined, and the existing-account path. It also covers client-identity limitations and post-account usage, leaving an agent with enough context to invoke the tool correctly.

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

Parameters5/5

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

The schema already covers both parameters well, and the description adds meaning beyond it: email must belong to the person owning the project, the key is only released after link confirmation, and existing addresses produce a link_account code instead of a new account. The name parameter's default is also called out.

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?

The description clearly states the tool creates an account and returns a permanent API key after a two-step verification flow. It distinguishes itself from sibling link_account by explaining when each is used, and it gives concrete statuses and behaviors. The verb and resource are unambiguous.

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

Usage Guidelines5/5

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

The description gives explicit step-by-step usage: call once with an email, wait for confirmation, then call again with the same email and client. It also tells the agent when to use link_account instead, and warns against creating a second account for an existing address. This is strong, decision-relevant guidance.

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

All Galley Render toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources