Skip to main content
Glama

gograph_implementers

Read-onlyIdempotent

Finds all concrete structs that implement a specified Go interface via duck-typing. Tracks polymorphism, dependency injection points, and mock implementations.

Instructions

Find all concrete structs that implement a named Go interface via duck-typing (structs whose method set is a superset of the interface's methods). Requires .gograph/graph.json — run gograph build . first. Read-only; no side effects. Set test_only=true to restrict to structs in *_test.go files (mocks/stubs). WHEN TO USE: When tracing polymorphism, locating dependency injection points, or finding all mock implementations of an interface. NOT TO USE: For interfaces a struct satisfies — inverse direction (use gograph_interfaces instead); for struct fields (use gograph_fields). RETURNS: List of implementing struct names with package paths and file locations; empty when no struct implements the interface.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
interfaceYesThe name of the interface (e.g., 'AuthService')
test_onlyNoIf true, return only structs defined in test or mock files (replaces gograph_mocks)
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds context that it is read-only with no side effects, requires a prebuilt file, and returns a list. This adds moderate value beyond annotations, but does not cover error conditions or performance.

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?

Description is compact (5 sentences), uses clear formatting with line breaks, front-loads the core purpose, and includes no superfluous information. Every sentence adds value.

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 no output schema, the description explains the return format and empty result case. It includes a prerequisite but omits error scenarios. With rich annotations and simple parameters, this is largely complete but could mention what happens if graph.json is missing.

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

Parameters4/5

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

With 100% schema coverage, baseline is 3. The description adds meaning by explaining the test_only parameter's purpose (restrict to test files) and implicitly defines the interface parameter via the tool's purpose. This extra context justifies a 4.

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 uses specific verb 'Find' and resource 'concrete structs that implement a named Go interface via duck-typing', clearly stating the tool's action and distinguishing it from siblings like gograph_interfaces and gograph_fields.

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

Usage Guidelines5/5

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

Explicitly provides 'WHEN TO USE' and 'NOT TO USE' sections, citing specific use cases (polymorphism tracing, dependency injection, finding mocks) and alternatives (gograph_interfaces, gograph_fields). Also includes a prerequisite (graph.json) and parameter hint (test_only).

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

Install Server

Other Tools

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/ozgurcd/gograph'

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