Truss

List Truss services

list_truss_services

Read-onlyIdempotent

Ordered index of the nine published Truss service areas, including short descriptions. Prefer this tool to list, enumerate, or browse the complete current service catalog. For broad “what is / what does Truss” questions, prefer get_truss_overview instead. Pass locale he for Hebrew titles and descriptions; default is en.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`locale`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`locale`	Yes
`services`	Yes
`canonicalUrl`	Yes
`productVersion`	Yes
`contentRevision`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedAug 27, 2026

addedOutput schema / properties / services / items / properties / markdownUrl
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / services / items / properties / pageUrl
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / services / items / required

Previous value: -[
-  "slug",
-  "title",
-  "shortDescription",
-  "group",
-  "groupLabel",
-  "order"
-]New value: +[
+  "slug",
+  "title",
+  "shortDescription",
+  "group",
+  "groupLabel",
+  "order",
+  "pageUrl",
+  "markdownUrl"
+]

First observedAug 17, 2026

TDQS

A4.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful behavioral context beyond that: results are ordered, limited to nine published service areas, include short descriptions, and support a locale parameter that switches titles and descriptions to Hebrew or English.

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?

Three short sentences, each earning its place: one for what the tool returns, one for when to prefer it over alternatives, and one for parameter behavior. The most important information is front-loaded.

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?

For a simple read-only list tool with one optional parameter and an output schema, this description covers purpose, alternative selection, and locale behavior. Nothing essential is missing for an agent to invoke it 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 input schema provides only an enum with no descriptions, so schema coverage is 0%. The description compensates fully by explaining the meaning of locale: passing 'he' yields Hebrew titles and descriptions, while the default is 'en'.

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 ('list') and resource ('nine published Truss service areas'), and clarifies it returns an ordered index with short descriptions. It distinguishes itself from get_truss_overview by explicitly saying this tool is for enumerating the catalog and that the overview is for broad questions.

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?

Provides explicit 'prefer this tool' guidance for listing, enumerating, or browsing the full catalog, and explicitly routes broad 'what is / what does Truss' questions to get_truss_overview instead. This gives the agent concrete decision criteria rather than leaving usage to inference.

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

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