Rodin
Server Details
Find ~5 thinkers whose intellectual fingerprint matches a passage of text.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.6/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of confusion with other tools. The tool's purpose is clearly distinct and unambiguous.
The single tool follows a clear verb_noun pattern ('find_thinkers_like'), and consistency is trivially maintained.
The server has only one tool, which is on the lower end of the range. While it serves a specific purpose, the count feels thin and could benefit from additional supporting tools.
The tool covers the primary use case of finding similar thinkers based on text. It returns sufficient information including a profile URL. However, missing features like browsing all thinkers or detailed profiles represent minor gaps.
Available Tools
1 toolfind_thinkers_likeFind thinkers like thisAInspect
Given a passage of text (essay, note, message, snippet, transcript), returns ~5 humans whose intellectual fingerprint matches it — recurring themes, mental models, archetypal stance, blind spots. Use when the principal asks for sparring partners, intellectual peers, "who else is wrestling with this," "who thinks like X," or "find me writers similar to this passage." Each result returns a name, three-word archetype, one-line summary, dominant themes, and a profile URL the principal can visit. The match runs over Voyage 3.5-lite text embeddings reranked by a proprietary 12-dimensional cognitive-style vector — so results align by how a mind reasons, not just topical overlap.
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| rerank | Yes | |
| matches | Yes |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
In the absence of annotations, the description fully discloses behavioral traits: it details the matching process (Voyage 3.5-lite embeddings reranked by a proprietary 12-dimensional cognitive-style vector) and clarifies that results align by reasoning style. It also enumerates return fields (name, archetype, summary, themes, URL).
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is moderately long but front-loaded with the core purpose. Every sentence contributes value, though it could be slightly more concise. The structure is logical: purpose, use cases, output format, and methodology.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity, the description is complete: it explains input content, output details (name, archetype, summary, themes, URL), and the underlying methodology. With an existing output schema, the description does not need to reiterate return types.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema coverage, the description compensates by explaining the 'text' parameter: a passage of text such as an essay, note, message, snippet, or transcript. It adds contextual meaning but does not mention the length constraints (min 80, max 8000 characters) from the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: given a passage of text, it returns approximately 5 humans whose intellectual fingerprint matches. The verb 'find' and resource 'thinkers' are specific, and the description differentiates it from hypothetical siblings by focusing on cognitive-style matching rather than topical overlap.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly lists use cases (e.g., sparring partners, intellectual peers) and explains what each result contains. While it does not provide negative examples or alternatives, it effectively guides the agent on when to invoke this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
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
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!