Skip to main content
Glama

Read a CMeIn information page

cmein_info
Read-only

Reads one of CMeIn's own information pages and returns its text with the link: "pricing" — what CMeIn costs — credit packs, the price of one photo, and that there is no subscription; "examples" — the gallery of generated photos, by scene, and whose photos they are; "faq" — how many reference photos are needed, whether results look like you, what happens to uploads, whether dating apps allow them; "about" — who builds CMeIn and why it only does candid realism; "refund" — when a refund applies, the time limit, and how to ask for one; "careers" — whether CMeIn is hiring and what it would hire for; "guides" — the guides index — longer how-to writing on taking and choosing profile photos; "bestAngle" — how to choose which photo to lead with, what a photographer actually judges in a portrait, and the free tool that scores and ranks up to six of your photos; "terms" — the terms of service; "privacy" — the privacy policy — what is collected and what happens to uploaded photos. Read live at request time, so terms, policies and open roles are current rather than remembered. No account needed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "topic": "<topic>"
    },
    "name": "cmein_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesWhich page to read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / topic / enum
      Previous value: -[
      -  "pricing",
      -  "examples",
      -  "faq",
      -  "about",
      -  "refund",
      -  "careers",
      -  "guides",
      -  "terms",
      -  "privacy"
      -]New value: +[
      +  "pricing",
      +  "examples",
      +  "faq",
      +  "about",
      +  "refund",
      +  "careers",
      +  "guides",
      +  "bestAngle",
      +  "terms",
      +  "privacy"
      +]
  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 establish readOnlyHint and openWorldHint, and the description adds genuinely new behavior: content is read live at request time so terms, policies and open roles are current rather than cached, and no account is required. It also states the return shape (page text with the link), though it says nothing about failure modes for unavailable pages.

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-loaded with verb and resource, and the long enumeration is justified by ten enum values with no filler sentences. The single run-on sentence with embedded semicolon list is dense and harder to scan than a short list would be, which keeps it below a 5.

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 one-parameter read-only tool with no output schema, the description covers what is returned, freshness guarantees, auth requirements, and per-topic content. Nothing an agent needs in order to call it correctly is missing.

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% and the enum is self-documenting at the label level, yet the description expands every one of the ten values with concrete content detail (e.g. "refund" — when it applies, the time limit, how to ask), which materially helps topic selection beyond "Which page to read."

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?

Specific verb ("Reads") plus resource ("one of CMeIn's own information pages") plus a full enumeration of the ten topics and what each contains. An agent can tell exactly what it gets 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 Guidelines3/5

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

Usage is only implied: the topic list lets an agent infer which page answers which question, but there is no explicit when-to-use guidance and no mention of overlapping siblings such as cmein_pricing, see_examples, or photo_advice, which cover adjacent ground.

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