Frank

Create a product in Frank

create_product

Creates a product in the user's Frank account. A product is the thing being researched — check list_products first, and only create one when nothing suitable exists.

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>",
      "description": "<description>",
      "category": "<category>"
    },
    "name": "create_product"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	What the product is called.
`urls`	No	Product or landing page URLs.
`brief`	No	Longer context for the interviewer. Falls back to description.
`category`	Yes	Which kind of product this is.
`description`	Yes	What the product does, in a sentence or two.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds the account-scoping context and a duplicate-avoidance rule, but says nothing about what happens on near-duplicate names or what the call returns (no output schema exists). Adequate but thin beyond the structured data.

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 sentences, zero filler, with the definition and the dedupe precondition front-loaded before any detail. Every clause carries information an agent would otherwise have to infer.

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 creation tool with full schema coverage and clear annotations, the description covers purpose, scope and the main usage pitfall. The one real gap is the absence of an output schema paired with no mention of what a successful create returns (e.g. the new product identifier needed for link_product or create_research).

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% with five well-described parameters including a 16-value category enum, so the schema does the heavy lifting. The description adds no field-level meaning (e.g. how brief interacts with description, or url format expectations) beyond what is already documented.

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 specific verb and resource ('Creates a product in the user's Frank account') and then defines the domain term ('the thing being researched'), which is not obvious from the name. It also names the sibling list_products, so an agent can place it among the product-related tools 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 Guidelines5/5

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

Explicitly routes the agent: check list_products first, and only create when nothing suitable exists. This is a concrete precondition plus a named alternative, which is exactly the guidance an agent needs before a non-idempotent write.

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

All Frank 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?