Skip to main content
Glama
asopitech-labs

Global Executables

by asopitech-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Search executable names

search_executables
Read-onlyIdempotent

Discover indexed command names across npm, PyPI, and other ecosystems with prefix, length, and provider filters.

Instructions

Discover indexed command names matching prefix, length, ecosystem, and provider filters.

    Use this for exploration; use check_executable for exact collisions and
    search_similar_executables for confusable names. All active filters intersect; ecosystem and
    scope.ecosystem must both match, so conflicting values return none, and limit applies only
    after deterministic case-insensitive sorting with case-sensitive tie-breaking. Do not use an
    empty result to infer availability: the tool makes no live registry call and fails instead of
    returning partial data when a required derived index is missing or corrupt.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of sorted results to return.
scopeNoOptional provider filters: source_type, package_system, distribution_family, distribution, distribution_release, language, registry, or ecosystem. All supplied key-value pairs must match; scoped negative results remain non-exhaustive.
lengthNoOptional exact character length of the executable name.
prefixNoCase-sensitive command-name prefix. Leave empty to search all indexed names subject to the other filters and limit.
ecosystemNoOptional exact provider ecosystem identifier, for example npm, pypi, homebrew, debian, or ubuntu.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.2
    • addedInput schema / properties / ecosystem / description
      Added value: +"Optional exact provider ecosystem identifier, for example npm, pypi, homebrew, debian, or ubuntu."
    • addedInput schema / properties / length / description
      Added value: +"Optional exact character length of the executable name."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of sorted results to return."
    • addedInput schema / properties / prefix / description
      Added value: +"Case-sensitive command-name prefix. Leave empty to search all indexed names subject to the other filters and limit."
    • addedInput schema / properties / scope / description
      Added value: +"Optional provider filters: source_type, package_system, distribution_family, distribution, distribution_release, language, registry, or ecosystem. All supplied key-value pairs must match; scoped negative results remain non-exhaustive."
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description adds substantial context beyond them: no live registry call, failure rather than partial data when the derived index is missing or corrupt, deterministic case-insensitive sort with case-sensitive tie-breaking, and that limit applies only after sorting.

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?

Front-loads the purpose and the sibling routing before the operational caveats. Dense but every sentence carries distinct information; the sorting/limit clause is slightly detailed but not wasted.

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, return values need no explanation, and the description covers the remaining gaps an agent needs: filter intersection behavior, non-live data caveat, failure mode, and ordering guarantees.

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?

Schema coverage is 100%, so baseline is 3, but the description adds genuine cross-parameter semantics not present in the schema: all active filters intersect, ecosystem and scope.ecosystem must both match, and conflicting values return none. It does not add per-parameter syntax beyond that.

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?

States a specific verb and resource ('Discover indexed command names') plus the exact filter dimensions (prefix, length, ecosystem, provider). It explicitly differentiates itself from siblings: check_executable for exact collisions and search_similar_executables for confusable names.

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?

Gives explicit when-to-use ('this for exploration'), names two alternatives with their distinct conditions, and adds a when-not caveat ('Do not use an empty result to infer availability'). The routing guidance is unambiguous.

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