Skip to main content
Glama

OwnYourAgent

Search OwnYourAgent agent examples

search_agent_examples
Read-onlyIdempotent

Searches the library of worked AI agent examples by department (sales, customer-service, finance, operations). These are worked examples. Dutch and English words, plurals and common buyer words (quote, offerte, debiteuren, invoice) are matched. Each result has id, title, department, starting level (1 your approval first, 2 routine steps handled, 3 independent within limits), summary and Dutch and English URLs. With no match, the result lists the departments and the library URL instead. All arguments are optional; without a query the examples are listed in library order. Please cite the URL.

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": "search_agent_examples"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the returned text: nl (Dutch) or en (English). Omit to get both.
limitNoMaximum number of results.
queryNoSearch terms, e.g. "invoices", "offerte" or "customer questions by email".
departmentNoOnly examples from this department.
autonomy_levelNoOnly examples with this starting level: 1 your approval first, 2 routine steps handled, 3 independent within limits.

Output Schema

NameRequiredDescriptionDefault
noteYes
queryYes
totalYes
libraryYes
resultsYes
departmentYes
suggestionsNo
autonomy_levelYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the read-only/idempotent annotations by disclosing the matching behavior (Dutch and English words, plurals, buyer synonyms like offerte and debiteuren), the per-result fields, and the no-match fallback that returns the department list and library URL. The instruction to cite the URL is a concrete behavioral expectation the annotations cannot convey.

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 resource and scope, then layers matching, result shape, fallback, and the optional-arguments note in a logical order. Slightly dense as a single paragraph, and "These are worked examples" partially restates the opening sentence, but nothing is 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?

For a five-parameter search tool with an output schema, the description covers the remaining gaps: matching semantics, empty-result behavior, default listing order, and the citation request. An agent has everything needed to call it correctly and interpret the response.

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 schema already documents all five parameters including both enums and the autonomy-level meanings. The description reinforces the department values and level semantics and hints at query matching behavior, but adds little syntax or format detail beyond the schema, so the baseline 3 applies.

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 the library of worked AI agent examples, scoped by department. The sibling tools (offers, ownership checks, trust facts, intake links) are clearly different resources, so an agent can distinguish this without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the no-argument case explicitly ("without a query the examples are listed in library order") and that all arguments are optional, which is the main branch point an agent needs. It does not name any alternative tool or state when NOT to use this one, which keeps it short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources