INITE

What INITE sells, and for how much

inite_services

Read-onlyIdempotent

INITE's services as a ladder, cheapest first: each step's id, name, price in the reader's currency and one line. slug gives one step in full, full: true all of them: what it delivers, how long it takes, the kind of price, the refund, and how it starts (a call with inite_book_call or a page to open).

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": "inite_services"
  }
}

Input Schema

Name	Required	Description
`full`	No	true: every step in full instead of the summary.
`lang`	No	The reader's language; sets the currency (pt quotes reais) and the copy. Default en.
`slug`	No	One step in full, by the id the summary gives, e.g. "local".

Output Schema

Name	Required	Description	Default
`lang`	No
`total`	Yes
`summary`	No
`currency`	No
`services`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 3, 2026

addedInput schema / properties / full

Added value: +{
+  "description": "true: every step in full instead of the summary.",
+  "type": "boolean"
+}

addedInput schema / properties / slug

Added value: +{
+  "description": "One step in full, by the id the summary gives, e.g. \"local\".",
+  "maxLength": 40,
+  "type": "string"
+}

addedOutput schema / properties / lang
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / summary
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / total
```
Added value: +{
+  "type": "integer"
+}
```

changedOutput schema / required

Previous value: -[
-  "services"
-]New value: +[
+  "services",
+  "total"
+]

First observedOct 20, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds real behavior beyond that: language drives currency (pt quotes reais), what each step's full record includes (delivery, duration, price kind, refund, how it starts), and how a step connects to `inite_book_call`. It stops short of mentioning caching or ordering guarantees beyond 'cheapest first'.

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?

One compact sentence pair with the core purpose front-loaded and mode selection following. The dense backtick-heavy phrasing packs a lot into few words, though the second clause runs long and could be broken for readability.

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 an output schema present, the description only needs to explain purpose, modes and defaults — all of which it does. All three optional parameters are accounted for, and the cross-reference to inite_book_call closes the loop on next steps.

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 earns more by tying parameters to each other — `slug` must be an id the summary returns, and `lang` changes both currency and copy, with en as the default. That relational meaning is not spelled out in 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?

The description gives a concrete verb and resource — INITE's services as a ladder, cheapest first — plus exactly what each step contains (id, name, price, one line). It also separates the three modes (default summary, `slug`, `full: true`), so an agent can tell it apart from siblings like inite_book_call or inite_guides without reading the 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?

It clearly states when to use each mode: bare call for the summary, `slug` for one step in full, `full: true` for all of them. It also points at the sibling `inite_book_call` as how a step starts. It doesn't explicitly say when NOT to reach for this tool versus inite_guides, but the context is unambiguous.

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

All INITE 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.