Skip to main content
Glama
zerotrust-labs

Solodit MCP Server

Official
by zerotrust-labs
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

Server Quality Checklist

67%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v1.0.0

  • Disambiguation5/5

    The two tools have clearly distinct purposes: one searches across findings with filters, the other retrieves a specific finding by ID. There is no overlap or ambiguity.

    Naming Consistency5/5

    Both tool names follow the same verb_noun pattern using snake_case: search_findings and get_finding_by_id. This is consistent and predictable.

    Tool Count3/5

    With only two tools, the set feels minimal but reasonable for a focused read-only API. The scope is narrow, yet two tools could be seen as slightly thin; however, they cover the core needs.

    Completeness4/5

    The tool surface covers the essential operations for accessing Solodit findings: searching and retrieving by ID. Minor gaps exist, such as no explicit listing endpoint, but search with filters effectively fills that role.

  • Average 3.4/5 across 2 of 2 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • No community issues in the last 6 months
    • 0 commits in the last 12 weeks
    • No stable releases found
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI is passing

  • This repository is licensed under MIT License.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • Add a glama.json file to provide metadata about your server.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • Behavior2/5

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

    No annotations are provided, so the description must disclose behavioral traits. It only says 'Get detailed information' without specifying what 'detailed' includes, whether the operation is read-only, how errors are handled (e.g., not found), or any other behavioral context. This leaves significant room for ambiguity.

    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 a single, concise sentence that is front-loaded with the action and target. Every word is relevant and there is no redundant or filler content.

    Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

    Completeness3/5

    Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

    For a simple lookup tool with one parameter, the description is adequate but incomplete. It does not describe the return format or the degree of detail, and without an output schema, this information is missing. The differentiation from sibling 'search_findings' is only implicit, so there is room for more contextual guidance.

    Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

    Parameters3/5

    Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

    The parameter description ('The finding ID or slug to search for') matches the tool description and already exists in the schema. Since schema description coverage is 100%, the description does not add additional meaning or clarify parameter formats beyond what the schema provides.

    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's function with a specific verb ('Get') and resource ('finding by its ID or slug'). It distinguishes this tool from the sibling 'search_findings' by focusing on retrieving a single, specific finding rather than performing a search.

    Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

    Usage Guidelines2/5

    Does the description explain when to use this tool, when not to, or what alternatives exist?

    The description gives no explicit guidance about when to use this tool instead of 'search_findings'. It implies usage for looking up a known finding by ID/slug, but does not mention exclusions or alternatives, so the agent is left to infer the appropriate context.

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

  • Behavior2/5

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

    No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that it searches and filters, without mentioning return format, pagination behavior, sorting defaults, authentication needs, or how filters combine. The schema documents parameters, but the description adds little beyond the verb and resource.

    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 two sentences long, front-loads the core purpose, and contains no filler or redundant information. Every word contributes meaning.

    Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

    Completeness2/5

    Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

    With 17 optional parameters and no output schema, the description is under-specified. It does not explain what the returned findings look like, how multiple filters interact, or what the default sorting and pagination behavior is. The description says 'and more' without elaboration, leaving critical context missing for a complex search tool.

    Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

    Parameters3/5

    Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

    Schema description coverage is 100%, so the baseline is 3. The description mentions filters for keywords, impact, firms, tags, and protocols, which maps to several parameters, but it adds no additional semantic detail beyond what the schema already provides. The phrase 'and more' is vague.

    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 searches Solodit for smart contract security findings and vulnerabilities, using a specific verb and resource. It distinguishes itself from the sibling get_finding_by_id by being a search/filter tool rather than a direct lookup.

    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 for searching and filtering findings but provides no explicit guidance on when to prefer this over get_finding_by_id or when not to use it. No alternatives are mentioned, leaving usage context implicit.

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

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

solodit-mcp MCP server

Copy to your README.md:

Score Badge

solodit-mcp MCP server

Copy to your README.md:

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zerotrust-labs/solodit-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server