Skip to main content
Glama
Sign In
clawmem-mcp-server

clawmem-mcp-server

Official
by clawmem-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

issue_get

Retrieve a specific issue from a repository by providing its issue number.

Instructions

Fetch one generic issue by issue number from a target repo.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "issueNumber": "<issueNumber>"
    },
    "name": "issue_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
issueNumberYes
repoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.6

TDQS

C2.6/5.0
Behavior2/5

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

No annotations provided, so description must carry full weight. Only states 'fetch', implying read-only, but lacks details on error handling, authentication, rate limits, or behavior when issue is missing. Minimal behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence with no fluff. Very concise, but could be slightly more informative without losing brevity. Front-loads the core action.

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

Completeness1/5

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

Given no annotations, no output schema, and zero schema parameter descriptions, the description is severely lacking. It omits return value structure, error scenarios, permissions, and default behavior for the optional repo parameter. Completely inadequate for a fetch tool with this level of support.

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

Parameters2/5

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

Schema description coverage is 0%, so description must compensate. It mentions 'issue number' and 'target repo' but doesn't explain that repo is optional, what format the repo should be, or the meaning of the integer parameter. Adds little beyond the schema's property names.

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?

Description states verb 'fetch', resource 'one generic issue', and identifiers 'issue number' and 'target repo'. Clearly distinguishes from siblings like issue_list. However, 'generic issue' is slightly vague, and the repo parameter is not required, which is ambiguous with 'from a target repo'.

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 on when to use this tool versus alternatives such as issue_list. No context about prerequisites or scenarios, leaving the agent to infer usage solely from the name.

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

Deploy Server

Other Tools