goji_browse_glossaryList GOJI's plain-English glossary — every term, across AI Visibility, Websites, Measurement, AI Builds and Brand. Filter by category to get each short definition as well as the name.
| Name | Required | Description | Default |
|---|---|---|---|
| category | No | Omit for the full A–Z index |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full disclosure burden. It does state the output shape ('each short definition as well as the name') and the non-mutating verb 'List' implies a read-only operation. It doesn't cover ordering guarantees, behavior for categories with no terms, or how the listed items connect to goji_explain_term, but for a simple browse tool the disclosed behavior is adequate.
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?
Two tight sentences with the verb front-loaded; both sentences earn their place. The category list slightly duplicates the schema enum and the title overlaps with the first clause, but the overall structure is compact and readable.
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 low-complexity tool with one optional parameter and no output schema, the description covers scope, filtering behavior, and return contents. The only real gaps are minor: whether A–Z ordering applies to filtered results and how the list relates to the sibling explain-term tool.
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?
Schema coverage is 100% and the parameter carries its own description ('Omit for the full A–Z index'), so the baseline is 3. The description adds a little meaning by stating what filtered output contains (short definitions plus names), but it mostly reiterates what the schema enum already communicates.
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?
The description uses a specific verb ('List') and a clear resource (GOJI's plain-English glossary terms), and names all five category scopes plus the output content. It conveys the browse-and-list function distinctly from the sibling goji_explain_term, though it never explicitly names that contrast, which keeps it one step short of a 5.
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?
The only usage guidance is implied: browse all terms or filter by category. With a closely-related sibling like goji_explain_term (presumably for explaining a single term) and goji_search available, the description gives no explicit when-to-use guidance, no exclusions, and no pointer to the alternative that handles one-term lookups.
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.
Tools map to distinct content types (FAQ, glossary, guide, chapter, service), and descriptions give clear usage cues. goji_answer_faq and goji_search overlap in content coverage, but their intended use cases ('best for how much/how long' vs 'use first when you don't know the page') reduce ambiguity.
Eight tools use the goji_ prefix with a clear verb_noun structure (answer_faq, browse_glossary, explain_term, get_service, read_guide, read_guide_chapter, start_enquiry). goji_guide_contents is a noun phrase and goji_search is a bare verb, so the pattern is not perfectly uniform.
Nine tools is a reasonable, focused set for a content-retrieval and enquiry server. Each tool covers a distinct access pattern—search, list, read, explain, and contact—without bloat.
The surface covers FAQ lookup, glossary browsing, term explanation, service info, guide TOC and chapter reading, and enquiry submission. Agents can navigate from general search to specific pages and then take a contact action, leaving no dead ends.