HireSquire Agent Ecosystem

create_checkout_session

Generate a Stripe Checkout URL for manual credit purchase. Use this to provide the human user with a secure payment link in the chat.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_checkout_session"
  }
}

Input Schema

Name	Required	Description	Default
`pack`	No	The desired credit pack.
`amount`	No	Custom amount (min $5.00).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedMay 16, 2026

changedInput schema / properties / amount / description

Previous value: -"Custom amount to purchase (min $5)"New value: +"Custom amount (min $5.00)."

changedInput schema / properties / pack / description

Previous value: -"Credit pack to purchase"New value: +"The desired credit pack."

addedInput schema / required
```
Added value: +[]
```

First observedMay 11, 2026

TDQS

A3.5/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 disclose that a Checkout Session is created server-side on Stripe, whether the link expires, what the agent should do with the URL afterward (present it, not fetch it), or what happens if neither parameter is supplied given both are optional.

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?

Two short sentences, both front-loaded with the action and the intended use. There is no filler or restatement of the tool name.

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 two-parameter, non-destructive link generator with no output schema, the description covers purpose and where to put the result. It is a bit thin on the optionality of both parameters and the resulting precedence rule, but nothing essential is missing.

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. The description adds a small amount of meaning by framing the parameters as a credit-purchase choice, and the enum values are self-documenting in the schema; it still does not explain the pack vs. amount relationship or which one takes precedence.

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?

States a specific verb and resource: "Generate a Stripe Checkout URL for manual credit purchase." It clearly distinguishes itself from a direct-purchase flow by the word "manual," but it never names purchase_credits, the obvious sibling, so the contrast is implied rather than stated.

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

Usage Guidelines3/5

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

Gives a usage context ("provide the human user with a secure payment link in the chat"), which is a real when-to-use signal. However, it never says when NOT to use it or why an agent would pick this over purchase_credits for buying the same credit packs, leaving the key routing decision to inference.

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

All HireSquire Agent Ecosystem tools Inspect

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

Need Help?