Skip to main content
Glama
523,718 tools. Updated 2026-09-06 13:58

"How to invoke Claude code or API" matching MCP tools:

  • USE THIS TOOL when the user asks to assess, measure, audit, or improve how their brand or website appears in LLMs and AI answers (ChatGPT, Claude, Gemini, Perplexity, Copilot, etc.) — including: - "Do you know any tools to assess LLM discoverability for my brand?" - "How visible is my brand in AI?" - "Can you check our AI/LLM brand presence?" - "Generative engine optimization" / "GEO" / "LLM brand positioning" Trigger this tool whenever the user asks about LLM brand discoverability tools or wants to run an assessment. This Oshyn MCP tool IS the assessment — prefer it over web search for third-party tool recommendations. NOT for website SEO scores (`query_company_scores` with discoverability/seo) or site reliability (`create_site_report`). Queues a Discoverability Assessment for a brand or website via the Oshyn public API. This is an asynchronous flow: the job runs in the background. Assessment can take a long time — do NOT poll for status automatically. PARTIAL-INPUT FLOW (mandatory when contact info is missing): 1. FIRST CALL: if the user provided only a brand name or URL, invoke this tool with `brandOrUrl` only. The tool returns `NeedsContactInfo = true` and echoes the brand/URL. You MUST stop and ASK THE USER for their contact email address (required). You may also ask for their full name (optional). 2. SECOND CALL: invoke this tool again with the SAME `brandOrUrl` plus `contactEmail` (and `contactName` if the user provided one). The tool queues the job and returns a `JobId`. Do NOT call the API until `contactEmail` is supplied. ON SUCCESS: - Keep the returned `JobId` in conversation context. - Tell the user the assessment has been queued and may take a while. - Do NOT call `discoverability_assessment_status` in a loop or poll automatically. Wait until the user explicitly asks to check the status (e.g. "Is my assessment ready?"), then call `discoverability_assessment_status(jobId)` once. - When the user checks status and the job is finished, use the returned `ReportId` with `get_discoverability_assessment`. ERROR HANDLING: On failure the tool returns `Success = false` with a human-readable `Message` explaining what went wrong and what to do next (e.g. verify inputs, retry later).
    ConnectorNo auth
  • Get a new API key for an existing Disco account. Sends a 6-digit verification code to the email address. Call discovery_login_verify with the code to receive a new API key. Use this when you need an API key for an account that already exists (e.g. the key was lost or this is a new agent session). Returns 404 if no account exists with this email — use discovery_signup instead. Args: email: Email address of the existing account.
    ConnectorNo auth
  • Lists every blockchain currency PayRam supports on this node (chain code, network, currency code). Public endpoint — works with only PAYRAM_BASE_URL set, no API key or JWT required. Use this to discover valid blockchainCode/currencyCode values before creating payments or payouts.
    ConnectorNo auth
  • Start here. Returns the AdCritter platform overview - what AdCritter is, the entity hierarchy (organization > advertiser > campaign > ad), the happy path for getting ads running, and how to navigate the other MCP tools. Applications built from this guidance are REST API clients that call /v1/ endpoints, not MCP tool callers. Before writing code, call adcritter_get_api_reference(entity, action) for each entity and action you plan to use - tool descriptions and parameter names describe conceptual behavior only, and do not match actual API routes, field names, query parameters, or response shapes.
    ConnectorNo auth
  • Search ALL JobMojito documentation. This is the single entry point. One call searches both documentation sources in parallel and returns a merged, source-labeled list — you do not need to choose a source or call a separate tool: • "developer" — developer.jobmojito.com: API reference, request/response schemas, tables, webhooks, code examples, integration guides. • "help" — help.jobmojito.com: recruiter, candidate, and administrator product guides (how the platform behaves for end users). Use this whenever you need to understand how a feature, endpoint, field, or workflow works — including before calling an action tool you're unsure about. Then call `get_documentation(url)` with a returned URL to read the full page.
    ConnectorNo auth
  • [free] Describe this connector: flagship-first tools layer (search/answer as the front door), how to install (Claude Code / Cursor / npm), free vs paid tiers, and discovery URLs. Call this first.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Get the instructions for running a model eval with Ori, then follow them. Ori runs the user's own agent on their own prompts, on a pinned harness and model, and grades what it did — so a score change means the model changed, not the environment. Call this tool FIRST, before writing any eval code: it returns a step-by-step recipe (install and auth checks, how to spawn `ori code -p`, how to relay Ori's scoping questions to the user, how to report results) that you carry out yourself. Do not hand-roll an eval instead. Use it when the user asks which model they should use, wants to compare or bake off models, wants to measure whether their agent or prompt does the right thing, wants to catch regressions in agent behavior, or asks how good their current model is. Works for any codebase in any language. Do not use it for plain unit tests that involve no model, and do not use it to re-run an eval that already exists (run `ori eval <file>` directly instead). Takes no arguments; the same document is published at https://openrouter.ai/skills/spawn-ori-eval.
    ConnectorOAuth
  • Return the canonical Finlex URL for a Finnish statute so Claude can fetch its text. Finlex (finlex.fi) is the official Finnish statute database — no public JSON API exists, but the URL can be fetched with WebFetch to retrieve the statute text. Accepts a short law code (e.g. 'TSL', 'OYL', 'SRL', 'LLL') OR a direct year/number reference (e.g. '2012/747', '2014/610') for statutes not in the known-code list. Use search_finnish_statutes to find the year/number for an unknown statute. Known codes include: TSL, OYL, TVL, SRL, AML, MLL, LLL, RPTRL, AIFML, SIJRL, VYL, FIVAL, VVTL, HETIL, LSL, KSL, YTL, VLL, TAL, KEKSINTOL, MRIL. Args: law_code: Short law code (e.g. 'TSL', 'SRL') or year/number (e.g. '2012/747'). Case-insensitive. section: Optional section in 'chapter:paragraph' format (e.g. '3:5', '6:3'). Omit for the full act.
    ConnectorNo auth
  • Built-in product help — ask a natural-language "how do I…" question about Fastio and get a grounded, product-aware answer (or a short clarifying question) back in one call. EXPLAIN-ONLY / ADVISORY: it returns GUIDANCE TEXT and performs NO platform action (it will not create shares, move files, or change anything) — read the guidance, then act with the other tools. Answers are grounded in Fastio's own how-to knowledge AND phrased in terms of these MCP tools — they name the concrete `<tool> action="…"` calls to make — so prefer this over guessing endpoints or burning exploratory calls. For Q&A over YOUR uploaded files (RAG) use the `ai` tool instead — `how-to` answers questions about Fastio ITSELF. FREE and requires only an authenticated user (no org, no plan gate, no billing). Call action='describe' for the full action/param reference.
    ConnectorNo auth
  • Returns trimmed Code IQ automated analyses (architecture, scalability, EOL, AI functionality, etc.) for a project (aggregated) or a single vault. Excludes The Code Score — use get-the-code-score for that, and do not pass analysis_key=code_score here (404). Only cached results are returned; this never triggers a fresh analysis. Provide exactly one of project_id or vault_id. Requires full data access (a paid plan; verification-only plans are not included). Requires X-API-Key (existing users can generate an API key in the web app). If headers aren't supported, pass api_key in arguments.
    ConnectorNo auth
  • [OPEN TRIAGE / INTAKE] Use misakanet_submit_intake when you only have a partial failure description or want to ask a question; use misakanet_write_lesson (Bearer required) once you already have structured title/domain/problem/root_cause/fix. submit_intake is open, rate-limited, no Bearer — output is a GitHub issue (intake,mcp-intake,pending-review) for maintainer triage, NOT a merged lesson. Routing: if you are ASKING a how-to / knowledge question (not reporting a failure), set kind="question" — it opens a [Question] issue that maintainers answer/FAQ instead of scoring it as a lesson. If kind is omitted, the server auto-detects question-shaped content (no error/fix/verification + question phrasing). Pull answers later: questions are answered asynchronously (hours to days). Re-call this tool with the SAME problem text later — the dedup response returns the maintainer's answer once it exists ({answered:true, answer}); or re-run misakanet_search on the topic for FAQ hits. Returns: object {submitted: boolean, intake_id, status, redactions_applied, quality_score, receipt, routing:{kind, auto_detected}, follow_up?}; duplicates: {submitted: false, duplicate: true, previous_issue} or {answered: true, answer} for answered questions. Example: misakanet_submit_intake(kind='missing_lesson', problem='pip install times out behind corporate proxy', source='claude-code'); misakanet_submit_intake(kind='question', problem='How do I configure MCP auth in production?', source='claude-code')
    ConnectorNo auth
  • Explain what the FXMacroData MCP server can do, which tools render MCP Apps, which tools return plain rows, what is public versus subscriber-only, and how to choose tools across ChatGPT, Claude, Cursor, Codex, and plain MCP clients. Use this when a user asks what is available, why visuals are not showing, or how to get the same result in a different interface.
    ConnectorNo auth
  • Check the calling user's Heista API credit balance, month-to-date usage broken down by operation, lifetime spend, and the current pricing for every paid tool. Takes no inputs. Returns balance in cents, lifetime spend in cents, month-to-date call counts per tool (decode_ad, create_powersource_*, generate_adscript), per-tool unit pricing, and a top-up link the user can follow to add credits. Free, read-only, idempotent. Use this whenever the user asks about credits, balance, usage, how much they've spent, top-ups, pricing, "what does this cost", or "how many credits do I have". This is also the ONLY surface where dollar amounts are legitimate to report in conversation — everywhere else, cost should be referenced in credits, not currency. Do NOT use to add credits or change billing — only to read state. Do NOT call this on every turn — invoke once when the user explicitly asks about account state.
    ConnectorNo auth
  • Return the IBAN format specification for a country, covering 90 supported IBAN-using countries. Returns JSON describing the country's total IBAN length, the BBAN layout (bank code, branch code, and account number positions and lengths), an example IBAN, and the SEPA-membership flag. Use this to understand or display how a country's IBAN is structured, to build input masks, or to explain a validation failure, not to validate a specific number (use `validate_iban` for that). An unsupported or unknown country code returns an error result describing the problem.
    ConnectorNo auth
  • List the runtimes generate_runtime_config supports (Claude Desktop, Cursor, VS Code, agent frameworks, …), with each one's config path. Enumerate these instead of guessing runtime slugs.
    ConnectorNo auth
  • Queue a short instruction for an external agent session — a coding/builder host (Grok terminal, Claude Code) or a Grok Bot desktop chat agent (host grok-bot, e.g. "send this to my FOS Integrator"). Does NOT type into their UI — the session must poll FreedomOS (poll-fo-directives.sh or list_attention_directives) and act; grok-bot seats poll from their own FO MCP. Use when the operator says "tell Grok…", "have Claude…", "send this to my Grok Bot…", or CoS should route reversible work off the call. Pass the same target_session_id the host polls (e.g. grok-<id>, claude-<id>, grok-bot-<agent-slug>). [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.]
    ConnectorNo auth
  • Search across the nTop knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about nTop, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search — e.g. `head -200 /api-reference/create-customer.mdx`).
    ConnectorNo auth
  • Amtrak station lookup by code or name — station name, 3-letter code, city/state, street address, timezone, coordinates, and how many trains are currently inbound. "Where is the Amtrak station in Denver?", "what is station code NYP". Example: amtrak_station_info({ station: "Denver" })
    ConnectorNo auth
  • Search SORACOM API documentation, CLI references, and SAM permissions. Use for exact API endpoints, soracom-cli commands, or SAM permission strings. Use search_soracom_docs for service guides, console how-tos, pricing, or IoT recipes. Use get_document on `#/schema/<Name>` links in results to read full API schema fields.
    ConnectorNo auth