Skip to main content
Glama

Close Crm

by io.github.pipeworx-io

Generate llms.txt

generate_llms_txt
Read-onlyIdempotent

Generate a production-ready llms.txt file for any URL so AI crawlers (ChatGPT, Claude, Perplexity) can index the site cleanly. Fetches the page, extracts title/description/key links, and emits the standard llms.txt markdown format. Output is a single text blob ready to drop at site-root/llms.txt. Useful for: getting a client's site indexed by AI, drafting llms.txt for your own project, or auditing how an AI crawler would see a competitor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesFull URL of the site to summarize, e.g. "https://example.com" or a specific landing page.
max_linksNoMaximum number of link entries to include (default 25, max 50).

TDQS

A4.1/5.0
Behavior4/5

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

Annotations indicate read-only, idempotent, non-destructive. The description adds context by explaining the fetching and extraction process, which aligns with annotations. No contradiction.

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 a single paragraph of about 60 words, front-loaded with the main action. It is efficient, though a bit redundant ('production-ready llms.txt file'). No wasted sentences.

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?

With two parameters and no output schema, the description explains the output format and use cases, providing sufficient context for a straightforward generation tool.

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 baseline is 3. The description adds value for the 'url' parameter with examples but does not elaborate on 'max_links' beyond what's in the schema.

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 clearly states the tool generates a production-ready llms.txt file for any URL, explaining the purpose for AI crawlers, the process (fetches page, extracts info, emits markdown), and output format. No confusion with sibling tools.

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

Usage Guidelines4/5

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

The description explicitly lists use cases: getting a client's site indexed, drafting for own project, or auditing competitor crawl. While it doesn't state when not to use, the guidance is clear and actionable.

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

All Close Crm toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

Multiple Pipeworx tools overlap significantly (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, entity_profile, compare_entities, recent_changes all query similar data). Close CRM tools are distinct but the overall set mixes two domains, causing confusion.

Naming Consistency2/5

Tool names mix snakes (close_get_lead), lowercase (ask_pipeworx), and descriptive phrases (scan_competitor_ai_presence). No consistent verb_noun pattern across the entire set.

Tool Count2/5

37 tools is excessive for a focused server. The combination of Close CRM and Pipeworx data services creates scope creep; many tools could be separate servers.

Completeness3/5

Pipeworx tools offer extensive data coverage, but Close CRM lacks update/delete operations for leads, contacts, and opportunities, leaving basic CRUD gaps.

Resources