Skip to main content
Glama
Sign In

NestDaddy

by com.nestdaddy
OverviewDiscussionsAdmin

software

Read-onlyIdempotent

Software and developer tools with their current version, updated daily (Homebrew installs of the last 30 days): name, description, category, platform, latest_version, install command (in tags) and link. query: optional words. category: all, development, productivity, design, security, utilities, multimedia, browser, communication, ai, cloud. sort: trending (most installed), latest (recently updated) or name. limit: 1-50.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "software"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoOrder: latest (newest first), trending (most used or played), name (A-Z) or rating.trending
limitNoHow many results to return, 1-50. Values outside the range are clamped.
queryNoOptional key words: a name, use, vendor or developer. Empty lists everything.
categoryNoall, development, productivity, design, security, utilities, multimedia, browser, communication, ai or cloud.all

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"all, development, productivity, design, security, utilities, multimedia, browser, communication, ai or cloud."
    • addedInput schema / properties / limit / description
      Added value: +"How many results to return, 1-50. Values outside the range are clamped."
    • addedInput schema / properties / query / description
      Added value: +"Optional key words: a name, use, vendor or developer. Empty lists everything."
    • addedInput schema / properties / sort / description
      Added value: +"Order: latest (newest first), trending (most used or played), name (A-Z) or rating."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, openWorld, non-destructive behavior, so the description's contribution is the data provenance and freshness: 'updated daily (Homebrew installs of the last 30 days)' and that install commands appear in tags. That is meaningful context an agent cannot get from the annotations. It still doesn't state result volume behavior or whether the daily update affects ordering.

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 definition is dense and front-loaded: the resource and its payload come first, then compact parameter glosses. A few items (the full field list, the enumerated categories) duplicate structured data and could be trimmed, but there is little wasted prose.

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 an output schema present, the description doesn't need to explain return shapes, yet it still sketches the fields and the data source. Combined with 100% schema coverage and full annotations, an agent has what it needs to call the tool correctly. Only the missing sibling routing guidance keeps it short of complete.

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 the baseline is 3. The description adds a useful gloss on 'trending' (most installed) and confirms the category and limit ranges, but it omits the 'rating' sort value present in the schema and its sort gloss ('latest = recently updated') differs slightly from the schema wording, so it adds modest rather than decisive meaning.

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?

The description opens with a specific verb-and-resource statement (a catalog of software and developer tools with current versions) and enumerates the returned fields (name, description, category, platform, latest_version, install command, link). An agent can tell this is a package/software directory lookup rather than a news or games search. It doesn't explicitly name the sibling tools it displaces, keeping it below a 5.

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?

Usage is only implied: 'query: optional words' plus 'Empty lists everything' tells the agent the query can be omitted, and the category/sort lists give browsing modes. There is no explicit statement of when to prefer this over ai_tools, games, or web_search, and no exclusions.

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

All NestDaddy toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources