Skip to main content
Glama

Google Big Query

by com.googleapis.bigquery
OverviewDiscussionsAdmin

get_job

Read-onlyIdempotent

Get information and status about a BigQuery job.

Use this tool to check the status, statistics, or configuration of a job using its job_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jobIdYesRequired. Job ID of the requested job.
locationYesRequired. The geographic location of the job.
projectIdYesRequired. Project ID of the requested job.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoOutput only. Opaque ID field of the job.
etagNoOutput only. A hash of this resource.
kindNoOutput only. The type of the resource.bigquery#job
statusNoOutput only. The status of this job. Examine this value when polling an asynchronous job to see if the job is complete.
selfLinkNoOutput only. A URL that can be used to access the resource again.
statisticsNoOutput only. Information about the job, including starting time and ending time of the job.
user_emailNoOutput only. Email address of the user who ran the job.
jobReferenceNoOptional. Reference describing the unique-per-user name of the job.
configurationNoRequired. Describes the job configuration.
jobCreationReasonNoOutput only. The reason why a Job was created.
principal_subjectNoOutput only. [Full-projection-only] String representation of identity of requesting party. Populated for both first- and third-party identities. Only present for APIs that support third-party identities.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / location / description
      Previous value: -"Optional. The geographic location of the job."New value: +"Required. The geographic location of the job."
    • changedInput schema / required
      Previous value: -[
-  "projectId",
-  "jobId"
-]New value: +[
+  "projectId",
+  "jobId",
+  "location"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / location / description
      Previous value: -"Required. The geographic location of the job."New value: +"Optional. The geographic location of the job."
    • changedInput schema / required
      Previous value: -[
-  "projectId",
-  "jobId",
-  "location"
-]New value: +[
+  "projectId",
+  "jobId"
+]
  3. Changed2 schema fields changed
    • changedInput schema / properties / location / description
      Previous value: -"Optional. The geographic location of the job."New value: +"Required. The geographic location of the job."
    • changedInput schema / required
      Previous value: -[
-  "projectId",
-  "jobId"
-]New value: +[
+  "projectId",
+  "jobId",
+  "location"
+]
  4. Changed2 schema fields changed
    • changedInput schema / properties / location / description
      Previous value: -"Required. The geographic location of the job."New value: +"Optional. The geographic location of the job."
    • changedInput schema / required
      Previous value: -[
-  "projectId",
-  "jobId",
-  "location"
-]New value: +[
+  "projectId",
+  "jobId"
+]
  5. Changed2 schema fields changed
    • changedInput schema / properties / location / description
      Previous value: -"Optional. The geographic location of the job."New value: +"Required. The geographic location of the job."
    • changedInput schema / required
      Previous value: -[
-  "projectId",
-  "jobId"
-]New value: +[
+  "projectId",
+  "jobId",
+  "location"
+]
  6. Changed2 schema fields changed
    • changedInput schema / properties / location / description
      Previous value: -"Required. The geographic location of the job."New value: +"Optional. The geographic location of the job."
    • changedInput schema / required
      Previous value: -[
-  "projectId",
-  "jobId",
-  "location"
-]New value: +[
+  "projectId",
+  "jobId"
+]
  7. Changed2 schema fields changed
    • changedInput schema / properties / location / description
      Previous value: -"Optional. The geographic location of the job."New value: +"Required. The geographic location of the job."
    • changedInput schema / required
      Previous value: -[
-  "projectId",
-  "jobId"
-]New value: +[
+  "projectId",
+  "jobId",
+  "location"
+]
  8. Changed2 schema fields changed
    • changedInput schema / properties / location / description
      Previous value: -"Required. The geographic location of the job."New value: +"Optional. The geographic location of the job."
    • changedInput schema / required
      Previous value: -[
-  "projectId",
-  "jobId",
-  "location"
-]New value: +[
+  "projectId",
+  "jobId"
+]
  9. Changed2 schema fields changed
    • changedInput schema / properties / location / description
      Previous value: -"Optional. The geographic location of the job."New value: +"Required. The geographic location of the job."
    • changedInput schema / required
      Previous value: -[
-  "projectId",
-  "jobId"
-]New value: +[
+  "projectId",
+  "jobId",
+  "location"
+]
  10. Changed2 schema fields changed
    • changedInput schema / properties / location / description
      Previous value: -"Required. The geographic location of the job."New value: +"Optional. The geographic location of the job."
    • changedInput schema / required
      Previous value: -[
-  "projectId",
-  "jobId",
-  "location"
-]New value: +[
+  "projectId",
+  "jobId"
+]
  11. Changed2 schema fields changed
    • changedInput schema / properties / location / description
      Previous value: -"Optional. The geographic location of the job."New value: +"Required. The geographic location of the job."
    • changedInput schema / required
      Previous value: -[
-  "projectId",
-  "jobId"
-]New value: +[
+  "projectId",
+  "jobId",
+  "location"
+]
  12. Changed2 schema fields changed
    • changedInput schema / properties / location / description
      Previous value: -"Required. The geographic location of the job."New value: +"Optional. The geographic location of the job."
    • changedInput schema / required
      Previous value: -[
-  "projectId",
-  "jobId",
-  "location"
-]New value: +[
+  "projectId",
+  "jobId"
+]
  13. Changed2 schema fields changed
    • changedInput schema / properties / location / description
      Previous value: -"Optional. The geographic location of the job."New value: +"Required. The geographic location of the job."
    • changedInput schema / required
      Previous value: -[
-  "projectId",
-  "jobId"
-]New value: +[
+  "projectId",
+  "jobId",
+  "location"
+]
  14. Changed2 schema fields changed
    • changedInput schema / properties / location / description
      Previous value: -"Required. The geographic location of the job."New value: +"Optional. The geographic location of the job."
    • changedInput schema / required
      Previous value: -[
-  "projectId",
-  "jobId",
-  "location"
-]New value: +[
+  "projectId",
+  "jobId"
+]
  15. Changed2 schema fields changed
    • changedInput schema / properties / location / description
      Previous value: -"Optional. The geographic location of the job."New value: +"Required. The geographic location of the job."
    • changedInput schema / required
      Previous value: -[
-  "projectId",
-  "jobId"
-]New value: +[
+  "projectId",
+  "jobId",
+  "location"
+]
  16. Changed2 schema fields changed
    • changedInput schema / properties / location / description
      Previous value: -"Required. The geographic location of the job."New value: +"Optional. The geographic location of the job."
    • changedInput schema / required
      Previous value: -[
-  "projectId",
-  "jobId",
-  "location"
-]New value: +[
+  "projectId",
+  "jobId"
+]
  17. Changed2 schema fields changed
    • changedInput schema / properties / location / description
      Previous value: -"Optional. The geographic location of the job."New value: +"Required. The geographic location of the job."
    • changedInput schema / required
      Previous value: -[
-  "projectId",
-  "jobId"
-]New value: +[
+  "projectId",
+  "jobId",
+  "location"
+]
  18. Changed1 schema field changed
    • addedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Added value: +{
+  "$ref": "#/$defs/SecureContext",
+  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
+}
  19. Changed1 schema field changed
    • removedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Removed value: -{
-  "$ref": "#/$defs/SecureContext",
-  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
-}
  20. Changed1 schema field changed
    • addedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Added value: +{
+  "$ref": "#/$defs/SecureContext",
+  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
+}
  21. Changed1 schema field changed
    • removedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Removed value: -{
-  "$ref": "#/$defs/SecureContext",
-  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
-}
  22. Changed1 schema field changed
    • addedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Added value: +{
+  "$ref": "#/$defs/SecureContext",
+  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
+}
  23. Changed1 schema field changed
    • removedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Removed value: -{
-  "$ref": "#/$defs/SecureContext",
-  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
-}
  24. Changed1 schema field changed
    • addedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Added value: +{
+  "$ref": "#/$defs/SecureContext",
+  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
+}
  25. Changed1 schema field changed
    • removedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Removed value: -{
-  "$ref": "#/$defs/SecureContext",
-  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
-}
  26. Changed1 schema field changed
    • addedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Added value: +{
+  "$ref": "#/$defs/SecureContext",
+  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
+}
  27. Changed1 schema field changed
    • removedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Removed value: -{
-  "$ref": "#/$defs/SecureContext",
-  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
-}
  28. Changed1 schema field changed
    • addedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Added value: +{
+  "$ref": "#/$defs/SecureContext",
+  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
+}
  29. Changed1 schema field changed
    • removedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Removed value: -{
-  "$ref": "#/$defs/SecureContext",
-  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
-}
  30. Changed1 schema field changed
    • addedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Added value: +{
+  "$ref": "#/$defs/SecureContext",
+  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
+}
  31. Changed1 schema field changed
    • removedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Removed value: -{
-  "$ref": "#/$defs/SecureContext",
-  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
-}
  32. Changed1 schema field changed
    • addedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Added value: +{
+  "$ref": "#/$defs/SecureContext",
+  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
+}
  33. Changed1 schema field changed
    • removedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Removed value: -{
-  "$ref": "#/$defs/SecureContext",
-  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
-}
  34. Changed1 schema field changed
    • addedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Added value: +{
+  "$ref": "#/$defs/SecureContext",
+  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
+}
  35. Changed1 schema field changed
    • removedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Removed value: -{
-  "$ref": "#/$defs/SecureContext",
-  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
-}
  36. Changed1 schema field changed
    • addedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Added value: +{
+  "$ref": "#/$defs/SecureContext",
+  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
+}
  37. Changed1 schema field changed
    • removedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Removed value: -{
-  "$ref": "#/$defs/SecureContext",
-  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
-}
  38. Changed1 schema field changed
    • addedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Added value: +{
+  "$ref": "#/$defs/SecureContext",
+  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
+}
  39. Changed1 schema field changed
    • removedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Removed value: -{
-  "$ref": "#/$defs/SecureContext",
-  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
-}
  40. Changed1 schema field changed
    • addedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Added value: +{
+  "$ref": "#/$defs/SecureContext",
+  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
+}
  41. Changed1 schema field changed
    • removedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Removed value: -{
-  "$ref": "#/$defs/SecureContext",
-  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
-}
  42. Changed1 schema field changed
    • addedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Added value: +{
+  "$ref": "#/$defs/SecureContext",
+  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
+}
  43. Changed1 schema field changed
    • removedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Removed value: -{
-  "$ref": "#/$defs/SecureContext",
-  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
-}
  44. Changed1 schema field changed
    • addedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Added value: +{
+  "$ref": "#/$defs/SecureContext",
+  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
+}
  45. Changed1 schema field changed
    • removedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Removed value: -{
-  "$ref": "#/$defs/SecureContext",
-  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
-}
  46. Changed1 schema field changed
    • addedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Added value: +{
+  "$ref": "#/$defs/SecureContext",
+  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
+}
  47. Changed1 schema field changed
    • removedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Removed value: -{
-  "$ref": "#/$defs/SecureContext",
-  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
-}
  48. Changed1 schema field changed
    • addedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Added value: +{
+  "$ref": "#/$defs/SecureContext",
+  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
+}
  49. Changed1 schema field changed
    • removedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Removed value: -{
-  "$ref": "#/$defs/SecureContext",
-  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
-}
  50. Changed1 schema field changed
    • addedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Added value: +{
+  "$ref": "#/$defs/SecureContext",
+  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
+}
  51. Changed1 schema field changed
    • removedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Removed value: -{
-  "$ref": "#/$defs/SecureContext",
-  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
-}
  52. Changed1 schema field changed
    • addedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Added value: +{
+  "$ref": "#/$defs/SecureContext",
+  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
+}
  53. Changed1 schema field changed
    • removedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Removed value: -{
-  "$ref": "#/$defs/SecureContext",
-  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
-}
  54. Changed1 schema field changed
    • addedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Added value: +{
+  "$ref": "#/$defs/SecureContext",
+  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
+}
  55. Changed1 schema field changed
    • removedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Removed value: -{
-  "$ref": "#/$defs/SecureContext",
-  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
-}
  56. Changed1 schema field changed
    • addedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Added value: +{
+  "$ref": "#/$defs/SecureContext",
+  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
+}
  57. Changed1 schema field changed
    • removedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Removed value: -{
-  "$ref": "#/$defs/SecureContext",
-  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
-}
  58. Changed1 schema field changed
    • addedOutput schema / $defs / JobConfigurationExtract / properties / secureContext
      Added value: +{
+  "$ref": "#/$defs/SecureContext",
+  "description": "Optional. A set of key-value pairs representing the secure context. This can be used to pass sensitive or context-specific information. They can be retrieved via the SECURE_CONTEXT() function and used to modify the run-time behavior of an extract job on tables with row access policies."
+}
  59. Added
  60. Removed
  61. Added
  62. Removed
  63. Added
  64. Removed
  65. Added
  66. Removed
  67. Added
  68. Removed
  69. Added
  70. Removed
  71. Added
  72. Removed
  73. Added
  74. Removed
  75. Added
  76. Removed
  77. Added
  78. Removed
  79. Added
  80. Removed
  81. Added
  82. Removed
  83. Added

TDQS

Score is being calculated.

All Google Big Query 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