FindAgent

findagent_import_repo

Read-only

Pull the CALLER'S OWN GitHub repo (via their connected token) and return deterministic grounding (basics, languages, tech domains, detected tools + the hosts they reach, and what the repo IS — skills, actions, runnable code or instructions only — with the parts found) plus a field contract. Use the grounding as the basis, then run findagent_submission_wizard to walk the user through the listing step-by-step and finalize with findagent_create_draft — your own model does the synthesis (no FindAgent LLM cost). Read-only: nothing is persisted or executed. Works for PRIVATE repos: the pull runs server-side with your stored GitHub token, so your AI client never needs repo access.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ref`	No	Optional branch/tag/SHA. Defaults to the default branch HEAD.
`repo`	Yes	owner/repo or a github.com URL (must be readable by your connected GitHub token). Private repos you own work — the pull is server-side.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`repo`	No
`commit`	No
`grounding`	No
`instructions`	No
`field_contract`	No
`already_imported`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026
- changedOutput schema / properties / grounding / properties / code_bundle / properties / confidence / type
```
Previous value: -[
-  "number",
-  "string",
-  "null"
-]New value: +[
+  "object",
+  "number",
+  "string",
+  "null"
+]
```
Changed2 schema fields changedSep 26, 2026
- addedOutput schema / properties / grounding / properties / detected_components
```
Added value: +{
+  "type": "object"
+}
```
- addedOutput schema / properties / grounding / properties / detected_warnings
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
First observedSep 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true; the description goes further by confirming nothing is persisted or executed and explaining that private repos are handled server-side with the stored GitHub token so the AI client never needs repo access. This adds important security and privacy context beyond the annotations.

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?

The description is front-loaded with the core action and return value, then moves to workflow and behavioral details. It is dense but every clause earns its place, covering purpose, return shape, follow-on tools, read-only behavior, and private-repo handling. It could be slightly tighter, but it is not bloated.

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

Completeness5/5

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

With an output schema present, the description correctly focuses on purpose, workflow, and behavioral constraints rather than return format. Annotations cover read-only and open-world hints, the schema fully documents parameters, and the description supplies the missing contextual details: private-repo support, server-side token handling, and the intended downstream workflow. Nothing necessary for correct invocation is missing.

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 input schema has 100% description coverage for both parameters (repo and ref), so the schema already documents their semantics. The description repeats that the repo must be readable by the connected token and that private repos work server-side, which mirrors schema text rather than adding new parameter detail. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb and resource: 'Pull the CALLER'S OWN GitHub repo (via their connected token)'. It clarifies scope, including that it works for private repos, and distinguishes itself from generic listing by framing the pull as the caller's own token-connected repo. The agent knows exactly what this tool returns: deterministic grounding plus a field contract.

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?

The description gives explicit next steps: use the grounding as the basis, then run findagent_submission_wizard, and finalize with findagent_create_draft. It also clarifies that the caller's own model does the synthesis (no FindAgent LLM cost) and that the tool is read-only, which sets expectations for when this is the right first step. No alternative tools are explicitly excluded, but the workflow routing is clear.

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

All FindAgent tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?