open-context

open-context_get_go_info

Retrieve Go version release notes or library information by specifying version or import path. Data fetched from official sources and cached.

Fetch and cache information about specific Go versions or Go libraries from official sources

TableJSON Schema

Name	Required	Description
`type`	Yes	Type of information to fetch: 'version' for Go release info or 'library' for Go package/library info
`version`	No	Go version to fetch (e.g., '1.21', '1.22') when type is 'version', or library version when type is 'library'
`importPath`	No	Import path of the Go library (e.g., 'github.com/gin-gonic/gin') when type is 'library'

A3.7/5.0

Behavior3/5

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

Mentions caching behavior, but lacks disclosure on authentication, rate limits, or other traits, with no annotations to compensate.

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?

Single concise sentence with front-loaded purpose, no unnecessary words.

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?

Adequate but does not describe the output format or what information is returned, given no output schema.

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 coverage is 100%, so description adds no extra meaning beyond the schema's parameter descriptions.

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?

Description specifies fetching and caching info about Go versions or libraries, clearly distinguishing from siblings focused on other technologies.

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?

Implicitly for Go-related queries, but no explicit when-to-use or alternatives are given.

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

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

curl -X GET 'https://glama.ai/api/mcp/v1/servers/incu6us/open-context'

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