Skip to main content
Glama
hajifkd

inspirehep-mcp

by hajifkd
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Server Quality Checklist

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

  • Latest release: v0.1.0

  • Disambiguation5/5

    Each tool has a clearly distinct purpose: searching by author, full text, or title. There is no overlap in functionality, and an agent can easily tell them apart based on the search parameter.

    Naming Consistency5/5

    All tool names follow a consistent pattern: 'inspirehep_search_by_' followed by the search parameter (author, fulltext, title). This verb_noun structure is uniform and predictable throughout the set.

    Tool Count3/5

    With only 3 tools, the server feels thin for a literature search domain. While the tools cover basic search methods, the scope is limited, and more operations (e.g., filtering, sorting, or retrieving specific records) might be expected for a comprehensive search interface.

    Completeness2/5

    The tool surface is severely incomplete for a literature search server. It only offers search functionality without any way to retrieve, update, or manage records (e.g., get_by_id, list_results, or advanced filtering). This creates significant gaps that could lead to agent failures when trying to perform full workflows.

  • Average 3.2/5 across 3 of 3 tools scored. Lowest: 2.6/5.

    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 status not available

  • 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

  • Behavior3/5

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

    Annotations provide readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering safety and behavior. The description adds no behavioral context beyond this (e.g., rate limits, authentication needs, or what 'search' entails like pagination). However, it doesn't contradict annotations, so it meets the lower bar with annotations present.

    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, efficient sentence with no wasted words. It's front-loaded with the core purpose, making it easy to scan and understand quickly, though it lacks depth due to its brevity.

    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?

    Given the tool has an output schema (which handles return values), annotations cover behavioral traits, but schema description coverage is 0% and the description doesn't explain parameters or usage context. For a search tool with 1 parameter (though nested with multiple fields), the description is incomplete, failing to guide on input semantics or sibling differentiation.

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

    Parameters1/5

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

    Schema description coverage is 0%, meaning parameters are undocumented in the schema. The description provides no information about parameters (e.g., what 'author' expects, how to format names, or details on other inputs like 'limit' or 'year'). It fails to compensate for the lack of schema documentation, leaving parameters semantically unclear.

    Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

    Purpose3/5

    Does the description clearly state what the tool does and how it differs from similar tools?

    The description 'Search INSPIRE-HEP literature by author' clearly states the action (search) and resource (INSPIRE-HEP literature), but it's vague about scope and doesn't distinguish from siblings like inspirehep_search_by_fulltext or inspirehep_search_by_title. It doesn't specify what 'by author' means operationally (e.g., author names vs. IDs).

    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?

    No guidance is provided on when to use this tool versus the sibling tools (inspirehep_search_by_fulltext, inspirehep_search_by_title). The description implies it's for author-based searches, but there's no explicit comparison or context for choosing among search methods, nor any mention of prerequisites or limitations.

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

  • Behavior3/5

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

    Annotations already provide readOnlyHint=true, destructiveHint=false, openWorldHint=true, and idempotentHint=true, covering safety and idempotency. The description adds no behavioral context beyond this, such as rate limits, authentication needs, or result format details. However, it doesn't contradict annotations.

    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, efficient sentence with no wasted words. It's front-loaded with the core functionality ('Search INSPIRE-HEP literature by title'), making it easy to parse and understand immediately.

    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 rich input schema with full parameter descriptions, annotations covering key behavioral traits, and the presence of an output schema (which handles return values), the description is reasonably complete. It could improve by adding usage guidelines relative to sibling tools, but overall it provides adequate context for a search operation.

    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 0%, but the input schema includes detailed descriptions for all parameters (title, year, limit, sort_by_citation, large_collaboration). The description adds no parameter semantics beyond the schema, but the schema provides comprehensive documentation, establishing a baseline of 3.

    Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

    Purpose4/5

    Does the description clearly state what the tool does and how it differs from similar tools?

    The description clearly states the action ('Search') and resource ('INSPIRE-HEP literature'), specifying the search field ('by title'). It distinguishes from sibling tools that search by author or fulltext, though it doesn't explicitly contrast them in the description text itself.

    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 provides no guidance on when to use this tool versus alternatives like inspirehep_search_by_author or inspirehep_search_by_fulltext. It lacks context about appropriate use cases, prerequisites, or exclusions, offering only basic functional information.

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

  • Behavior3/5

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

    Annotations already provide readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering safety and behavior. The description adds no additional behavioral context (e.g., rate limits, auth needs, or what 'full text' search entails), but does not contradict annotations.

    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, efficient sentence with no wasted words, clearly front-loaded with the tool's purpose. It earns its place by succinctly conveying the core functionality.

    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 has annotations covering safety and behavior, an output schema exists, and the description is concise but clear, it is reasonably complete. However, it could better address parameter usage or search scope to fully compensate for low schema coverage.

    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 0%, but the description mentions 'full text' which aligns with the 'fulltext' parameter. However, it does not explain other parameters (e.g., limit, sort_by_citation) or add meaning beyond the schema's property descriptions. With 0% coverage, baseline is lower, but the description partially compensates by hinting at the key parameter.

    Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

    Purpose4/5

    Does the description clearly state what the tool does and how it differs from similar tools?

    The description clearly states the action ('Search') and resource ('INSPIRE-HEP literature') with the method ('by full text'). It distinguishes from sibling tools that search by author or title, though it could be more specific about what 'full text' encompasses (e.g., paper body vs metadata).

    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 context through 'by full text' versus siblings' 'by author' or 'by title', but lacks explicit guidance on when to choose this tool over alternatives or any prerequisites. The context is clear but not explicitly stated.

    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

inspirehep-mcp MCP server

Copy to your README.md:

Score Badge

inspirehep-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/hajifkd/inspirehep-mcp'

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