F
licenseNot graded
qualityC
maintenanceThe public MCP server for togo — docs, the plugin marketplace, and plugin submission, for any agent.
1
-
Truss
by il.co.trus
Server Details
Public MCP for Truss, Pniel Cohen's development & consultancy business: overview, services, contact
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Available Tools
4 toolsget_truss_informationGet Truss informationARead-onlyIdempotentInspect
Published Truss information by topic. Localized topics (overview, 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 get_truss_overview or topic overview for broad business understanding; prefer list_truss_services for the complete service catalog.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| topic | Yes | ||
| locale | No |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| locale | No | |
| canonicalUrl | Yes | |
| productVersion | Yes | |
| contentRevision | Yes |
TDQS
A4.7/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, open-world false, and non-destructive, so the description's extra value is its content-selection behavior: localized topics honor locale with en default, while language-independent topics ignore locale. This goes beyond the structured annotations, though it does not discuss error or omission behavior.
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 sentences, each carrying a distinct purpose: core behavior, locale semantics, and sibling routing. There is no repetition of schema or annotation content, and the most important scope statement is front-loaded.
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?
The output schema covers return values, and the description handles topic selection, locale behavior, and two of three sibling distinctions. It is slightly incomplete in not mentioning get_truss_service as an alternative, and 'topic overview' is mildly ambiguous, but overall an agent can call 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?
Schema coverage is 0%, but the description compensates by grouping the topic enum into localized vs language-independent sets and explaining the locale parameter's default and Hebrew option. Both parameters receive meaningful guidance beyond the raw enum values.
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 opens with 'Published Truss information by topic,' naming the resource and the organizing dimension. It also distinguishes the tool from get_truss_overview and list_truss_services by explicitly stating which alternative fits broad understanding and full service catalog, so an agent can tell this topic lookup apart from siblings.
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?
It tells the agent exactly when to prefer alternatives: get_truss_overview or the overview topic for broad business understanding, and list_truss_services for the complete service catalog. It also states when locale matters and the default, which is actionable selection guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_truss_overviewGet Truss overviewARead-onlyIdempotentInspect
High-level Truss business overview (same payload as truss://overview/{locale}). Prefer this tool for broad questions about Truss as a business and for broad questions about Pini’s professional work, capabilities, or what he does through Truss (for example "What is Truss?", "What does Truss do?", "Tell me about Truss", "What does Pini do?", "Tell me about Pini professionally"). Pass locale he for Hebrew; default is en.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| locale | No |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| title | Yes | |
| locale | Yes | |
| markdown | Yes | |
| canonicalUrl | Yes | |
| productVersion | Yes | |
| contentRevision | Yes |
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, and non-destructive behavior, so the bar is lower. The description adds useful behavioral context: it notes the payload is identical to a deep-link resource and explicitly states the locale default and how to request Hebrew, which is beyond what the schema enum conveys.
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 efficient sentences with no filler. The core purpose and payload equivalence are front-loaded, followed by usage guidance and parameter instructions. Every sentence earns its place, and the example queries help without bloating the description.
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 simple, one-optional-parameter read-only tool with an output schema, the description is largely complete. It covers purpose, scope, language handling, and default behavior. The only minor gap is not explicitly contrasting with the sibling tools, though the 'broad questions' framing implies differentiation.
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 bears the burden for parameter meaning. It compensates well by explaining the locale parameter: 'Pass locale he for Hebrew; default is en.' This gives the agent the key decision rule for the only parameter.
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 opens with a clear, specific verb and resource: "High-level Truss business overview." It also scopes the tool to broad questions about Truss and Pini's professional work with concrete example queries, making it easy to distinguish from more focused sibling tools.
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?
"Prefer this tool for broad questions about Truss as a business" gives explicit routing guidance for when to select this tool over alternatives. It stops short of naming sibling tools or stating when not to use it, but the 'prefer' framing and broad-vs-specific examples provide solid context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_truss_serviceGet a Truss serviceARead-onlyIdempotentInspect
One published Truss service area by slug. Default detail is overview (adds heroLead, overviewSummary, overviewFit, and relatedServices). Pass detail summary for the index card fields only, or full for page sections and fullMarkdown. Unknown slugs return not_found with knownSlugs. Pass locale he for Hebrew; default is en.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | ||
| detail | No | ||
| locale | No |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| slug | No | |
| error | No | |
| group | No | |
| order | No | |
| title | No | |
| locale | No | |
| pageUrl | No | |
| heroLead | No | |
| sections | No | |
| groupLabel | No | |
| knownSlugs | No | |
| markdownUrl | No | |
| overviewFit | No | |
| canonicalUrl | No | |
| fullMarkdown | No | |
| productVersion | Yes | |
| contentRevision | Yes | |
| overviewSummary | No | |
| relatedServices | No | |
| shortDescription | No |
TDQS
A4.6/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnly/idempotent annotations, the description discloses default detail behavior, the semantic difference between detail values, the error result for unknown slugs (not_found with knownSlugs), and locale default behavior. This gives an agent a clear model of how the tool behaves at runtime.
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?
The description is compact and front-loaded with the core operation, then efficiently explains the optional parameters and edge-case behavior. Every sentence contributes meaningful guidance without repetition or filler.
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 available, the description does not need to detail return values. It covers default behavior, all parameter options, and the unknown-slug error case, making it complete for a tool of this complexity.
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?
Schema coverage is 0%, so the description carries the full burden. It explains slug as the service area identifier, detail as summary/overview/full with distinct field outcomes, and locale as en default or he. This is far more semantic than the bare enum names 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 clearly states that the tool fetches a single published Truss service area by slug, using a specific verb and resource. This distinguishes it from sibling tools like list_truss_services, which presumably returns multiple services.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage: call when you have a slug and need one service area, optionally choosing detail level or locale. However, it never explicitly contrasts this tool with get_truss_information or list_truss_services, leaving the when-not-to-use guidance absent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_truss_servicesList Truss servicesARead-onlyIdempotentInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| locale | No |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| count | Yes | |
| locale | Yes | |
| services | Yes | |
| canonicalUrl | Yes | |
| productVersion | Yes | |
| contentRevision | Yes |
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.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
2 tool updates
- Changed
get_truss_information1 field changed- changed
Input schema / properties / topic / enumPrevious value: -[ - "identity", - "about", - "services", - "engagement", - "fit", - "faq", - "certifications", - "testimonials", - "clients", - "contact" -]New value: +[ + "overview", + "identity", + "about", + "services", + "engagement", + "fit", + "faq", + "certifications", + "testimonials", + "clients", + "contact" +]
- Added
get_truss_overview
2 tool updates
- Changed
get_truss_service9 fields changed- added
Input schema / properties / detailAdded value: +{ + "enum": [ + "summary", + "overview", + "full" + ], + "type": "string" +} - added
Output schema / properties / fullMarkdownAdded value: +{ + "type": "string" +} - added
Output schema / properties / heroLeadAdded value: +{ + "type": "string" +} - added
Output schema / properties / markdownUrlAdded value: +{ + "type": "string" +} - added
Output schema / properties / overviewFitAdded value: +{ + "type": "string" +} - added
Output schema / properties / overviewSummaryAdded value: +{ + "type": "string" +} - added
Output schema / properties / pageUrlAdded value: +{ + "type": "string" +} - added
Output schema / properties / relatedServicesAdded value: +{ + "items": { + "additionalProperties": false, + "properties": { + "markdownUrl": { + "type": "string" + }, + "pageUrl": { + "type": "string" + }, + "shortDescription": { + "type": "string" + }, + "slug": { + "type": "string" + }, + "title": { + "type": "string" + } + }, + "required": [ + "slug", + "title", + "shortDescription", + "pageUrl", + "markdownUrl" + ], + "type": "object" + }, + "type": "array" +} - added
Output schema / properties / sectionsAdded value: +{ + "items": { + "additionalProperties": false, + "properties": { + "id": { + "type": "string" + }, + "markdown": { + "type": "string" + }, + "title": { + "type": "string" + } + }, + "required": [ + "id", + "title", + "markdown" + ], + "type": "object" + }, + "type": "array" +}
- Changed
list_truss_services3 fields changed- added
Output schema / properties / services / items / properties / markdownUrlAdded value: +{ + "type": "string" +} - added
Output schema / properties / services / items / properties / pageUrlAdded value: +{ + "type": "string" +} - changed
Output schema / properties / services / items / requiredPrevious value: -[ - "slug", - "title", - "shortDescription", - "group", - "groupLabel", - "order" -]New value: +[ + "slug", + "title", + "shortDescription", + "group", + "groupLabel", + "order", + "pageUrl", + "markdownUrl" +]
3 tool updates
- First observed
get_truss_information - First observed
get_truss_service - First observed
list_truss_services
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Public portfolio MCP for resume, services, availability, project evidence, and introductions.
Public, read-only MCP server for FarmNeural company facts, packages, and capabilities.
Paid remote MCP for spec driven development acceptance gate MCP, structured receipts, audit logs, an
Dribba: services, case studies, budget estimates and contact, as MCP tools.
Related MCP Servers
- AlicenseAqualityAmaintenanceAn MCP server for freelancers and agencies that drafts client proposals and business emails — quotes, invoices, follow-ups, scope changes, and more — in your own voice, running locally with no API key or cloud.1002MIT
- AlicenseBqualityCmaintenanceMCP server to publish HTML/Markdown docs, upload assets, and reply to stakeholder comments on uselink.app directly from AI tools like Claude and Cursor.3417MIT
- AlicenseNot gradedqualityCmaintenanceA sovereign, MIT-licensed MCP server for professional-service workflows, providing offline-capable, Ed25519-signed tools for autonomous agents and human developers.MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.4/5.0
Disambiguation3/5
get_truss_information is a catch-all topic endpoint that overlaps with get_truss_overview for the overview topic and with list_truss_services for the services topic. The descriptions include clear preference guidance, but an agent still has to choose among these overlapping tools.
Naming Consistency4/5
Most tools follow a get_truss_<resource> pattern, with list_truss_services as the plural collection counterpart. The exception is get_truss_information, whose vague 'information' label doesn't clearly distinguish it from get_truss_overview or get_truss_service.
Tool Count4/5
Four tools is a reasonable size for a business-information server, covering overview, service catalog, service detail, and topic-specific content. The count is slightly inflated by the redundant get_truss_information, but it remains appropriately scoped.
Completeness5/5
The tool set provides broad coverage of the domain: a high-level overview, the complete service catalog with detail views, and many additional topics such as about, engagement, certifications, testimonials, clients, and contact. There are no obvious dead ends or missing operations for the stated purpose.