Skip to main content
Glama
Sign In

Programscape

by com.programscape
OverviewDiscussionsAdmin

Search startup programs and offers

search_programs
Read-onlyIdempotent

Searches the reviewed catalog of startup credits, programs, support and product discounts across providers (AWS, Google Cloud, Microsoft Azure, OpenAI, Anthropic, NVIDIA, Stripe and more). Each result carries its official source and the date it was last checked. Can be limited to programs whose product offers an agent-tool capability (search, scrape, crawl, browser, extract, llm or sandbox): a program matches when its record lists any one of those asked for, and results keep the catalog’s own order. A result lists its capabilities when its record has been reviewed for them. A listing is not a statement that anyone qualifies.

Input Schema

NameRequiredDescriptionDefault
kindNo"programs" for startup programs and support, "offers" for product discounts, "all" for both (the default).
limitNoHow many results to return (default 20, at most 50).
queryNoWords to match against program names, headlines, products and providers. Leave empty to list everything.
providerNoA provider id such as "aws", "gcp", "openai" or "stripe". Leave empty for every provider.
capabilitiesNoAgent-tool capabilities, e.g. ["search"] or ["scrape", "crawl"]. A program matches when its record lists any one of them. Leave it out to search every program, including those not reviewed for capabilities.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / capabilities
      Added value: +{
+  "description": "Agent-tool capabilities, e.g. [\"search\"] or [\"scrape\", \"crawl\"]. A program matches when its record lists any one of them. Leave it out to search every program, including those not reviewed for capabilities.",
+  "items": {
+    "enum": [
+      "search",
+      "scrape",
+      "crawl",
+      "browser",
+      "extract",
+      "llm",
+      "sandbox"
+    ],
+    "type": "string"
+  },
+  "maxItems": 7,
+  "minItems": 1,
+  "type": "array"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description only needs to add context — and it does: results carry an official source and last-checked date, results preserve the catalog's own order, capability data exists only for reviewed records, and it disclaims that a listing is not an eligibility statement. This is genuinely useful behavioral 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?

Four sentences, front-loaded with purpose and scope before the filtering rules; each sentence adds information. Slight redundancy with the schema's own capabilities description keeps it from a 5, but there is no filler.

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?

There is no output schema, and the description compensates by describing what a result contains (official source, last-checked date, capability list) and the ordering guarantee. Combined with 100% schema coverage and a full annotation set, an agent has everything needed to call it correctly.

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 the baseline is 3, but the description adds real semantics the schema lacks: capabilities match if the record lists ANY one of the requested values, and results retain catalog ordering. It also clarifies the default/empty behaviors implicitly, though the query/provider params are left to 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?

States a specific verb and resource (searches a reviewed catalog of startup credits, programs and discounts) and names the provider scope. It is clearly distinguishable from siblings like get_program (single lookup) and compare_programs (comparison) without opening a schema.

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?

The description implies when the tool fits (browsing/filtering the catalog) and explains the capability filter's matching rule, but it never states when to use this versus get_program or compare_programs, nor any exclusions. Usage is inferable rather than explicit.

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

All Programscape 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