Odile Gate

Create a Gate project

gate_create_project

Create a Free project in front of an existing HTTPS API. No signup or payment required. For a credential-free demo use https://sandbox.gate.odilelabs.com with GET /customers/:cid/tickets/:id (customer A holds tickets 1-3, B holds 4-5: try GET /customers/A/tickets/1). Returns project_id, admin_key (shown once) and the gateway base URL apps call instead of the API. A real API and its credentials need owner authorization.

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>",
      "upstream": "<upstream>"
    },
    "name": "gate_create_project"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	A name for the project, e.g. "Shop API"
`upstream`	Yes	The API base URL, https only, e.g. https://api.example.com/v1
`header_name`	No	Optional: the secret header your API expects, e.g. Authorization or apikey
`header_value`	No	Optional: its value. Stored encrypted; apps never see it.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A4.1/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, open-world write; the description adds genuinely new behavior: admin_key is shown only once, and apps receive the gateway base URL rather than the upstream. It omits the non-idempotency implication (repeat calls create duplicate projects), which is the remaining behavioral gap.

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?

Front-loaded with the core action and return values, then demo guidance. The demo path detail (customer A holds tickets 1-3) is useful but slightly verbose relative to a creation tool.

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?

No output schema exists, yet the description names the key return values (project_id, admin_key, gateway URL), which is what an agent needs. Annotations cover safety; only idempotency/duplicate-creation behavior is left unstated.

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 coverage is 100%, so all four parameters including the optional header pair are already documented. The description reinforces the https-only upstream constraint and adds a concrete demo example, but supplies no new syntax or semantics beyond the schema.

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 ("Create a Free project in front of an existing HTTPS API") plus scope (free tier, no signup). Reads clearly distinct from siblings like gate_add_app or gate_create_run.

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 concrete call-to-action context: use the supplied sandbox URL with a sample upstream for a credential-free demo, and notes owner authorization is needed for a real API. It never explicitly contrasts with sibling tools such as gate_add_app, so it stops short of full alternative routing.

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

All Odile Gate 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?