Skip to main content
Glama
Sign In

GlossGenius MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Find client in GlossGenius

glossgenius_find_client
Read-onlyIdempotent

Find client in the user's own GlossGenius account from ChatGPT, Claude or any AI agent. Returns how to do it in GlossGenius step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's GlossGenius Cloud Browser. GlossGenius's official API: GlossGenius has no public API, developer docs, webhooks or MCP server (checked 24 Oct 2026).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations, the description states that the tool opens nothing by itself and returns procedural instructions, which is important behavioral context for a read-only guide tool. It also explains the absence of a public GlossGenius API, reinforcing why browser tools are needed for execution.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core message is front-loaded, but phrases like 'from ChatGPT, Claude or any AI agent' and the dated API disclaimer add avoidable bulk. The description remains understandable, though it could be tighter and more direct.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter guide tool with no output schema, the description is largely complete: it says what is returned, that no action is performed, and which tool family to use next. It could still be clearer about the exact shape of the returned instructions, but the essential context is present.

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?

The tool has zero parameters, so there is no parameter semantics burden. The baseline for a zero-parameter tool is 4, and the description does not need to explain input fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (client) and account context (the user's own GlossGenius account), and it clarifies that the tool returns step-by-step instructions rather than performing the lookup itself. The opening 'Find client' wording is slightly misleading because the tool does not actually return client data, but the second sentence corrects that expectation.

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?

It gives clear next-step guidance: use this to get GlossGenius screens/buttons/fields, then act with cotlet_browser_* tools. It does not explicitly compare against sibling tools like cotlet_app_guide or the other GlossGenius tools, so alternatives and exclusions are left implicit.

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

All GlossGenius MCP Server and API by Cotlet 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