getting_startedStart here: platform overview, the proposal/approval operating model, auth rules, common flows, and agent etiquette. Static content — requires no scopes.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| auth | Yes | ||
| docs | Yes | ||
| welcome | No | ||
| platform | Yes | ||
| etiquette | Yes | ||
| common_flows | Yes | ||
| field_limits | Yes | ||
| operating_model | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description bears full responsibility. It states the content is static and requires no scopes, clearly indicating a read-only, safe operation with no authentication burden.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise: two sentences with no wasted words. Key information is front-loaded with 'Start here.'
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple static overview tool with zero parameters and an output schema, the description fully captures what the agent needs to know: it's the entry point with no side effects.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist, and schema coverage is 100%. The description adds value by clarifying the content is static and introductory, exceeding the baseline expectation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states it's a starting point for platform overview, operating model, auth rules, flows, and etiquette. It distinguishes itself from search or fetch tools by its introductory nature.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
"Start here" explicitly tells agents to use this first. It doesn't explicitly say when not to use, but the context of it being static overview makes it obvious it's not for data retrieval.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The search tools (search, projects_search, marketplace_listings_search) overlap significantly—search is explicitly an 'additive alias' over the other two, making them partially redundant. fetch, getting_started, and marketplace_listings_search are fairly distinct, but the search trio creates ambiguity about which to call for a given query.
Mixed conventions: projects_search and marketplace_listings_search follow verb_noun, but search, fetch, and getting_started are single words/varied patterns. Names are descriptive enough but lack a uniform verb_noun structure across the whole set.
Five tools is a reasonable size for a search/discovery-oriented server. The count feels slightly thin given the mention of several underlying operations (projects_get_deep_dive, marketplace_listing_get), but it's within a sensible scope for the apparent purpose.
Read-side coverage is decent: search, detail-fetch, and overview docs are all present. However, the server references get_deep_dive and get operations that aren't directly exposed as standalone tools, and there's no way to perform any writes/updates, leaving the surface feel like incomplete proxies for a broader API.