Truss

Get Truss information

get_truss_information

Read-onlyIdempotent

Published Truss information by topic. Localized topics (about, services, engagement, fit, faq) use locale, default en; pass he for Hebrew. Language-independent topics (identity, certifications, testimonials, clients, contact) ignore locale for content selection. Prefer list_truss_services for the service index.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`topic`	Yes
`locale`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`locale`	No
`canonicalUrl`	Yes
`productVersion`	Yes
`contentRevision`	Yes

TDQS

A4.3/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, so the safety profile is clear. The description adds valuable behavioral nuance about locale handling and topic categorization beyond what annotations or schema provide, ensuring the agent knows the tool's selection behavior.

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?

The description is brief at three sentences, with critical information front-loaded: purpose first, then parameter details, then usage guidance. Every sentence adds value with no redundancy, though it could be slightly tighter by combining locale details.

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?

Given the tool's moderate complexity (2 parameters, output schema exists), the description covers purpose, parameter semantics, usage guidance, and behavioral nuance (locale logic). The output schema reduces need to explain return values, making this adequately complete for a read-only information retrieval tool.

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 description coverage is 0%, so the description must compensate for the two parameters. It explains the meaning of the topic enum by dividing into two functional categories (localized vs. language-independent) and clarifies locale's purpose (default en, pass he for Hebrew). This adds substantial semantic value beyond the raw enum lists.

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 clearly states the tool fetches published Truss information by topic, identifying two categories of topics (localized vs. language-independent) and how locale affects them. This differentiates it from siblings by explaining the tool's coverage and topic handling.

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?

The description provides explicit guidance on when to use locale (for localized topics) and that language-independent topics ignore locale. It also explicitly directs the AI to prefer list_truss_services for the service index, giving a clear alternative for a subset of use cases.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation4/5

The tools are mostly distinct: list_truss_services provides an index, get_truss_service returns a single service by slug, and get_truss_information covers non-service topics. There is slight overlap because get_truss_information can include a 'services' topic, but the descriptions explicitly steer agents toward list_truss_services for that case.

Naming Consistency4/5

All tools follow a clear get_/list_ + truss_ object pattern with snake_case. The only minor inconsistency is singular 'service' versus plural 'services', but this is understandable since one fetches a single item and the other lists multiple items.

Tool Count4/5

Three tools is slightly lean but appropriate for a focused content-retrieval server. The tool count matches the apparent scope: listing services, fetching service details, and retrieving general informational content.

Completeness4/5

The surface covers the core read-only workflows: browsing the service index, viewing a specific service, and fetching topic-based information. There are no obvious missing operations for the apparent purpose, though it could theoretically benefit from a tool to list available information topics.

Resources

Need Help?